Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 11:30:56 +0100	[thread overview]
Message-ID: <20131031113056.03b1b6d5@skate> (raw)
In-Reply-To: <CAAXf6LVZW++12ECLBa0MoHUdjFKXdYy0ueoSk4a6WpvxYuAyJA@mail.gmail.com>

Dear Thomas De Schampheleire,

On Thu, 31 Oct 2013 11:13:33 +0100, Thomas De Schampheleire wrote:

> It would be great if we could add extra states to the patchwork
> configuration. I looked at the patchwork sources, which has an xml
> file with the different states, but it was unclear to me where this
> file is read, and whether it is project specific or patchwork-global.
> 
> Do note that it is possible to change the search filter, and specify
> 'Nobody' in the Delegate field. Since the search is HTTP/GET based,
> you can add this URL as a bookmark.
> http://patchwork.ozlabs.org/project/buildroot/list/?delegate=-

Interesting, thanks for looking into this.

> > 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.
> 
> I have no doubt on your good judgement here. I'm only considering what
> will happen if several people start acting as a maintainer-proxy. In
> patchwork, it will not be visible at all who has taken a given patch.
> Suppose that for some reason the maintainer-proxy forgets about the
> patch, then it will be lost unless the submitter notices it and pings.

I agree. I will try to update the patches and move them back into the
Delegate To state.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      parent reply	other threads:[~2013-10-31 10:30 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
2013-10-31 17:57               ` Arnout Vandecappelle
2013-10-31 10:30         ` Thomas Petazzoni [this message]

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=20131031113056.03b1b6d5@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