[Buildroot] [PATCH] arch/mips: Set BR2_GCC_TARGET_ARCH for MIPS

Thomas De Schampheleire patrickdepinguin at gmail.com
Thu Oct 31 10:13:33 UTC 2013


On Thu, Oct 31, 2013 at 10:22 AM, Thomas Petazzoni
<thomas.petazzoni at free-electrons.com> wrote:
> 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.

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=-

>
> 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.

Best regards,
Thomas


More information about the buildroot mailing list