From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] ympd: new package
Date: Tue, 23 Sep 2014 22:46:32 +0200 [thread overview]
Message-ID: <20140923224632.17a49f30@free-electrons.com> (raw)
In-Reply-To: <CABGWzsQ5K=n4Cobck__oRkppK9Aq0uyV2Nn03tO1J2kYOqjqaQ@mail.gmail.com>
Dear Eric Limpens,
Please keep the Buildroot list in Cc.
On Tue, 23 Sep 2014 22:28:10 +0200, Eric Limpens wrote:
> should I set the current patch to 'superseded' in patchwork? I'll send a
> new/revised version.
We usually set the state to "Superseded" once a new patch has been
sent. If we have requested some changes and we are fairly sure the
submitter is going to submit an updated version, then we usually set
the state to "Changes requested". But in fact, it doesn't make much
difference, as in both cases, the patch is no longer in the "New"
state, which means we no longer consider it as to be merged.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-09-23 20:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 19:53 [Buildroot] [PATCH 1/1] ympd: new package Eric Limpens
2014-09-23 20:02 ` Thomas Petazzoni
[not found] ` <CABGWzsQ5K=n4Cobck__oRkppK9Aq0uyV2Nn03tO1J2kYOqjqaQ@mail.gmail.com>
2014-09-23 20:46 ` Thomas Petazzoni [this message]
2014-09-23 21:02 ` Samuel Martin
-- strict thread matches above, loose matches on Subject: below --
2014-09-28 12:04 Eric Limpens
2014-10-04 12:42 ` 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=20140923224632.17a49f30@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.