From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Patchwork superseded patches
Date: Tue, 1 Oct 2013 21:57:58 +0200 [thread overview]
Message-ID: <20131001215758.29f06d76@skate> (raw)
In-Reply-To: <CAAXf6LW8YVfgiMDyu+PnYdMKA0Lh2BU6=DkPiCpORUWf+x1Adw@mail.gmail.com>
Thomas, Peter,
On Wed, 25 Sep 2013 11:16:47 +0200, Thomas De Schampheleire wrote:
> Here are some patches that can be marked as superseded in patchwork:
Thanks, all marked as superseded.
Peter, can you add Thomas DS to the list of people allowed to change
the status of patches in patchwork? I believe Thomas has a long track
record of BR contributions, and he is willing to help us triaging the
backlog of patches.
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-10-01 19:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-25 9:16 [Buildroot] Patchwork superseded patches Thomas De Schampheleire
2013-10-01 19:57 ` Thomas Petazzoni [this message]
2013-10-01 20:05 ` Peter Korsgaard
2013-10-02 7:28 ` Thomas De Schampheleire
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=20131001215758.29f06d76@skate \
--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