From: Otavio Salvador <otavio@ossystems.com.br>
To: OpenEmbedded Development Mailing List
<openembedded-devel@lists.openembedded.org>
Subject: Problems with current workflow using PatchWork
Date: Mon, 23 Mar 2009 05:47:36 -0300 [thread overview]
Message-ID: <873ad462xj.fsf@neumann.lab.ossystems.com.br> (raw)
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.
What others think?
--
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
next reply other threads:[~2009-03-23 8:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-23 8:47 Otavio Salvador [this message]
2009-03-24 15:46 ` Problems with current workflow using PatchWork Cliff Brake
2009-03-24 16:29 ` Otavio Salvador
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=873ad462xj.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;
as well as URLs for NNTP newsgroup(s).