[Buildroot] [PATCH] bluez5_utils: bumped version number to 5.25
Peter Seiderer
ps.report at gmx.net
Sun Nov 23 00:12:39 UTC 2014
Hello Vicente, Jaap,
On Fri, Nov 21, 2014 at 05:00:59PM +0000, Vicente Olivert Riera wrote:
> Dear Jaap Crezee,
[...]
> 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?
> 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
More information about the buildroot
mailing list