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 22:54:07 +0100 [thread overview]
Message-ID: <20131031225407.5e5e2e40@skate> (raw)
In-Reply-To: <CAAXf6LW4angtN30SpTaU=gOXP0r9YWHBug1-uVVgejnHcm1U=g@mail.gmail.com>
Dear Thomas De Schampheleire,
On Thu, 31 Oct 2013 18:10:36 +0100, Thomas De Schampheleire wrote:
> Ah, I had interpreted this branch according to the strategy discussed
> at last BDD regarding the community organization. In that discussion,
> such aggregation of submitted patches was also proposed. I thought you
> were acting in that mode.
>
> In that more general case, where there would me more than one
> maintainer-proxy, the exact strategy is still somewhat unclear to me.
I think the strategy for multiple maintainer-proxy hasn't been really
defined precisely. I believe that the thing we really believed in was
the addition of Acked-by/Tested-by information in the list of patches
in patchwork (both command line and web). This way Peter can much more
easily see which patches have received Acked-by/Tested-by, and look at
these with an higher priority. This would make the Acked-by/Tested-by
more useful, and potentially encourage us and others to do more of
those Acked-by/Tested-by.
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 21:54 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
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 [this message]
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=20131031225407.5e5e2e40@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