Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Getting patches committed
Date: Thu, 21 Jan 2010 07:45:49 -0500	[thread overview]
Message-ID: <4B584C7D.2040109@balister.org> (raw)
In-Reply-To: <201001211336.27857.ml@vdm-design.de>

On 01/21/2010 07:36 AM, Thomas Zimmermann wrote:
> Am Donnerstag 21 Januar 2010 13:15:21 schrieb Philip Balister:
>> On 01/21/2010 05:20 AM, Dr. Michael Lauer wrote:
>>> Am 21.01.2010 um 11:02 schrieb Holger Hans Peter Freyther:
>>>>> 2. Is there a way to have a staging branch where all patches are
>>>>> committed to, which have not been reviewed for let us say one week, to
>>>>> get more testing and before they go into the dev branch? Maybe it is
>>>>> easier for people to at least test build such a branch?
>>>>
>>>> Would you be interested in creating such a branch for us? I assume it is
>>>> certainly easier to git cherry-pick a patch than to download the mbox
>>>> and use git am..
>>>
>>> I fully agree. I'm neither using patchwork nor do I find patches on the
>>> list a good idea. I'd welcome for-oe-upstream trees that would contain
>>> patches that -- if good -- we could just pull from.
>>
>> I actually like patches on the list, because it makes me aware of how is
>> doing work and keeps me aware of the kinds of things people without
>> commit access are interested in. Also, it gives people with commit
>> access a forum for changes they would like reviewed.
>>
>> I am not opposed to someone creating a git branch or branches created
>> from list patches, but do not want to see the patches disappear from the
>> list.
>>
>> If the patch that was sent to the list comes from git-send-patch (I hope
>> I hve that correct) there is a script contrib/patchwork/git-am.sh that
>> makes it really easy to apply the patch.
>>
>> Philip
>
> I'm one of those without commit rights :)
> And i think the problem is, that nobody feels responsible for the patches on
> patchwork. I know this situation from SHR patchwork, when you don't ask
> someone directly to commit a patch from patchwork, nobody will do it.
> That's the only way it really works currently.
> I have 4 people with commit rights i can ask, so i have no problems but others
> probably doesn't know someone...
>
> I think a sort of moderator for patchwork is needed, that assosiats patches to
> the maintainer.

There is nothing wrong with nagging people on the list and on irc to 
commit your patch :) Sometimes I will commit stuff just because the 
author takes a little time to explain the patch to me.

Philip



  reply	other threads:[~2010-01-21 12:48 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-21  9:43 Getting patches committed Paul Menzel
2010-01-21 10:02 ` Holger Hans Peter Freyther
2010-01-21 10:20   ` Dr. Michael Lauer
2010-01-21 10:30     ` Holger Hans Peter Freyther
2010-01-21 12:15     ` Philip Balister
2010-01-21 12:36       ` Thomas Zimmermann
2010-01-21 12:45         ` Philip Balister [this message]
2010-01-21 19:06           ` Paul Menzel
2010-01-21 15:49         ` Konrad Mattheis
2010-01-21 19:10       ` Paul Menzel
2010-01-21 12:16     ` Rolf Leggewie
2010-01-21 12:34       ` Frans Meulenbroeks
2010-01-21 19:01         ` Paul Menzel
2010-01-21 19:48       ` Martin Jansa
2010-01-21 22:06         ` Stanislav Brabec
2010-01-21 22:00       ` Stanislav Brabec
2010-01-21 23:11         ` Rolf Leggewie
2010-01-22  0:13           ` Stanislav Brabec
2010-01-22  0:37             ` Rolf Leggewie
2010-01-22  0:40             ` Richard Purdie
2010-01-22  7:53             ` Holger Hans Peter Freyther
2010-01-22 11:44           ` Petr Štetiar
2010-01-22 14:53             ` Rolf Leggewie
2010-01-22 16:15               ` Petr Štetiar
2010-01-22 16:44                 ` Rolf Leggewie

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=4B584C7D.2040109@balister.org \
    --to=philip@balister.org \
    --cc=openembedded-devel@lists.openembedded.org \
    /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