Skip to contentSkip to conversation

bluez5_utils: bumped version number to 5.25

PATCH New Peter Seiderer 2 participants 2 messages Nov 23, 2014 – Nov 26, 2014

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 bluez5_utils: bumped version number to 5.25

Hello Vicente, Jaap,

Quoted 1 line · Vicente Olivert Riera

Dear Jaap Crezee,

[...]

Quoted 8 lines

Just a few more things for the next time you send patches to Buildroot. After sending a new version of a patch, we usually mark the former patch as "superseded" in patchwork. To be able to do that, you need to be logged in in patchwork. If you don't have an account, you can create one here:

http://patchwork.ozlabs.org/register/

Would be a nice patchwork feature to mark 'legacy' patches automatically as superseded in case a newer patch (with same subject, new version number, from same submitter) is detected on the mailing list?

Quoted 7 lines

Another one. When you create the patch using "git format-patch", before sending it, please edit the patch using your favourite text editor and add the version number in the "Subject" line. Here is an example using your own patch:

Subject: [PATCH v2] bluez5_utils: bumped version number to 5.25

Or use 'git format-patch --subject-prefix "PATCH v2" ...'

Regards,
Peter

#1 lore raw

PATCH 1/1 bluez5_utils: bumped version number to 5.25

Dear Peter Seiderer,

Quoted 6 lines · Peter Seiderer
Quoted 6 lines

Just a few more things for the next time you send patches to Buildroot. After sending a new version of a patch, we usually mark the former patch as "superseded" in patchwork. To be able to do that, you need to be logged in in patchwork. If you don't have an account, you can create one here:

Quoted 6 lines
Quoted 2 lines

http://patchwork.ozlabs.org/register/

Would be a nice patchwork feature to mark 'legacy' patches automatically as superseded in case a newer patch (with same subject, new version number, from same submitter) is detected on the mailing list?

There is a such a feature, but only if the new version of the patch series is sent as a reply to the previous one. And of course, it only works if each patch in the new version have exactly the same subject as in the previous version. That's why we never use it.

Thomas

Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com