Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Otavio Salvador <otavio@ossystems.com.br>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Problems with current workflow using PatchWork
Date: Tue, 24 Mar 2009 13:29:15 -0300	[thread overview]
Message-ID: <87hc1i51gk.fsf@neumann.lab.ossystems.com.br> (raw)
In-Reply-To: <f96d234e0903240846s37d4bc77lfe7b31a4d6806262@mail.gmail.com> (Cliff Brake's message of "Tue, 24 Mar 2009 11:46:44 -0400")

Cliff Brake <cliff.brake@gmail.com> writes:

> On Mon, Mar 23, 2009 at 4:47 AM, Otavio Salvador
> <otavio@ossystems.com.br> wrote:
>> Hello,
>>
>> Today I went to take a look if there were anything I could help with at
>> OE side and went to PatchWork to review pending patches and noticed a
>> cuple of issues.
>>
>>  - we need to do more review cycles at PatchWork and update the status
>>   according
>>
>>   There're applied patches that were not archived and patches that we
>>   asked for changes that hadn't the status changed to reflect it. This
>>   way PW loses the main feature that is trackability of patch status.
>>
>>   Please commiters, when doing a commit please remember to archive the
>>   patch at PW.
>>
>>  - merges need to be archived on PW
>>
>>   I noticed tha the RPM fixes went finally merged into the
>>   mainline. GREAT! But they were still listed as waiting for
>>   review. Since Marcin has commit, he did the merge but forgot to
>>   archive the whole set of patches at PW.
>>
>>   I suggest we when commiting our own patches take care of archiving
>>   them at PW to make life easier to everyone.
>
> Makes sense to me.  I have been archiving patches as I apply them, and
> selecting "Accepted".

Yes, some people has been doing it. I does it too.

However we _all_ need to do that or we lose time reviewing patches that
has already been applied.

-- 
Otavio Salvador                  O.S. Systems
E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854         http://projetos.ossystems.com.br



      reply	other threads:[~2009-03-24 16:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-23  8:47 Problems with current workflow using PatchWork Otavio Salvador
2009-03-24 15:46 ` Cliff Brake
2009-03-24 16:29   ` Otavio Salvador [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=87hc1i51gk.fsf@neumann.lab.ossystems.com.br \
    --to=otavio@ossystems.com.br \
    --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