From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] arch/mips: Set BR2_GCC_TARGET_ARCH for MIPS
Date: Thu, 31 Oct 2013 10:22:53 +0100 [thread overview]
Message-ID: <20131031102253.1aeaea28@skate> (raw)
In-Reply-To: <CAAXf6LVCOqiCdQfy+S_YRiA2c1fzGpip36=hM4c6M+cV=S47og@mail.gmail.com>
Dear Thomas De Schampheleire,
On Thu, 31 Oct 2013 10:19:01 +0100, Thomas De Schampheleire wrote:
> > Applied to for-peter-2013.11, a branch that I will ask Peter to pull
> > when he comes back. I will mark such patches as Accepted in patchwork,
> > making the (maybe optimistic) assumption that Peter will pull my entire
> > branch.
>
> Why not use the 'Delegated to' field in patchwork instead? It will
> keep the patch as New, until being applied, and it is clear whose
> branch it is in.
Could be a possibility indeed, but it means that I continue to see
these patches in patchwork. Admittedly with a different state, but it's
not as nice as not having them anymore.
I've been quite conservative on the patches I've taken (i.e no new
packages or version bumps), so I'm pretty confident that Peter should
take all of them.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-10-31 9:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-28 14:21 [Buildroot] [PATCH] arch/mips: Set BR2_GCC_TARGET_ARCH for MIPS Markos Chandras
2013-10-30 17:45 ` Thomas Petazzoni
2013-10-31 9:19 ` Thomas De Schampheleire
2013-10-31 9:22 ` Thomas Petazzoni [this message]
2013-10-31 10:13 ` Thomas De Schampheleire
2013-10-31 10:17 ` Arnout Vandecappelle
2013-10-31 10:47 ` Thomas Petazzoni
2013-10-31 12:45 ` Thomas De Schampheleire
2013-10-31 14:55 ` Thomas Petazzoni
2013-10-31 17:10 ` Thomas De Schampheleire
2013-10-31 21:54 ` Thomas Petazzoni
2013-10-31 17:57 ` Arnout Vandecappelle
2013-10-31 10:30 ` 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=20131031102253.1aeaea28@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