All of lore.kernel.org
 help / color / mirror / Atom feed
From: Graeme Russ <graeme.russ@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Application of patch submitted during the previous	Merge Window
Date: Fri, 23 Sep 2011 20:17:23 +1000	[thread overview]
Message-ID: <4E7C5CB3.2050009@gmail.com> (raw)
In-Reply-To: <4E7C59B4.50900@denx.de>

Hi Stefano,

On 23/09/11 20:04, Stefano Babic wrote:
> On 09/23/2011 11:21 AM, Graeme Russ wrote:

> Maybe we have to start updating patchwork directly after sending our
> answers to the ML to maintain the tool synchron. I was used to update
> patchwork after answering several messages to the ML and, well, it is
> common to forget to update some patches to the new status. It take more
> time, but the only way that works with me is to update patchwork after
> each answer, and not at the end...

I must admit, as a sole developer/custodian, I really do not know how much
work it is to update Patchwork in sync with the ML

>> Well I have a few niggles with Patchwork:
>>  - It failed to see one patch in one of my multi-patch series
>>  - Even though I kept the 'in-reply-to' chain intact, it still has the
>>    individual versions of my console patches (it should just update the
>>    existing patch)
>>  - I cannot even find phylib: remove a couple of redundant code lines
>>    (submitted 06/09/11 by Vladimir Zapolskiy <vz@mleia.com>)
> 
> I cannot see this patch on the mailing list, too. I can see a patch with
> the same name submitted a day before at 05/09/11. And I can find it in
> patchwork:
> 
> http://patchwork.ozlabs.org/patch/113414/

Ah, I see now - it has been accepted. Silly me :)

>>> Also any volunteers to help out.  There are many areas where help
>>> could be needed.
>>>
>>> - We need a new network custodian.
>>>
>>> - We could need some "trivial patch monkeys" that pick up trivial
>>>   patches (like cosmetic changes cleaning up coding style things etc.,
>>>   documentation changes etc.) so I just can pull that stuff.
>>
>> Maybe the load can be spread here - maintainers can put these in designated
>> branches in their repositories. I know this will cause the odd conflict,
>> but we (the maintainers) could also periodically sync between each other.
>> Another alternative is to create a new repo that all the custodians have
>> access to...
> 
> This makes things more complicated.....

Probably true. But we really need to collect these little patches somehow -
Wolfgang is just too busy and they fly right past him

Regards,

Graeme

  reply	other threads:[~2011-09-23 10:17 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-23  6:21 [U-Boot] Application of patch submitted during the previous Merge Window Graeme Russ
2011-09-23  7:25 ` Wolfgang Denk
2011-09-23  9:21   ` Graeme Russ
2011-09-23 10:04     ` Stefano Babic
2011-09-23 10:17       ` Graeme Russ [this message]
2011-09-23 10:23       ` Wolfgang Denk
2011-09-25 10:24         ` stefano babic
2011-09-23 10:18     ` Wolfgang Denk
2011-09-23 10:46       ` Graeme Russ
2011-09-25 19:55         ` Wolfgang Denk
2011-09-25 20:32           ` Graeme Russ
2011-09-30 22:40           ` Mike Frysinger
2011-11-15 15:01         ` [U-Boot] [STATUS] Help needed - urgently Wolfgang Denk
2011-11-16 18:51           ` [U-Boot] [STATUS] Custodians - please lend a hand Wolfgang Denk
2011-11-16 19:34             ` Stefano Babic
2011-11-16 19:48               ` Wolfgang Denk
2011-11-17 18:19               ` Detlev Zundel
2011-11-17 20:16                 ` Andy Fleming
2011-11-17 20:58                   ` Wolfgang Denk
2011-11-16 20:38           ` [U-Boot] [STATUS] Help needed - urgently Kumar Gala
2011-11-16 21:35             ` Wolfgang Denk
2011-11-17 12:40               ` Stefano Babic
2011-11-17 13:41                 ` Kumar Gala
2011-11-17 13:43               ` Kumar Gala
2011-11-17 14:10                 ` Wolfgang Denk
2011-11-17 14:54                   ` Kumar Gala

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=4E7C5CB3.2050009@gmail.com \
    --to=graeme.russ@gmail.com \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.