From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] bluez5_utils: bumped version number to 5.25
Date: Wed, 26 Nov 2014 23:01:19 +0100 [thread overview]
Message-ID: <20141126230119.75fb213d@free-electrons.com> (raw)
In-Reply-To: <trinity-621b72dd-4362-44df-bbf8-d19c6ffb5953-1416701559591@3capp-gmx-bs13>
Dear Peter Seiderer,
On Sun, 23 Nov 2014 01:12:39 +0100, Peter Seiderer wrote:
> > 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?
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
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-11-26 22:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-23 0:12 [Buildroot] [PATCH] bluez5_utils: bumped version number to 5.25 Peter Seiderer
2014-11-26 22:01 ` Thomas Petazzoni [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-11-30 14:37 Jaap Crezee
2014-11-30 14:40 ` Baruch Siach
2014-11-30 14:43 ` Jaap Crezee
2014-11-30 14:59 ` Baruch Siach
2014-12-02 7:19 ` Jaap Crezee
2014-12-07 23:03 ` Thomas Petazzoni
2014-11-21 16:36 Jaap Crezee
2014-11-21 17:00 ` Vicente Olivert Riera
2014-11-22 16:16 ` Thomas Petazzoni
2014-11-23 5:40 ` Baruch Siach
2014-11-24 10:04 ` Vicente Olivert Riera
2014-11-22 18:00 ` Thomas Petazzoni
2014-11-26 21:56 ` Thomas Petazzoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141126230119.75fb213d@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox