From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Patchwork housekeeping
Date: Thu, 22 Mar 2012 11:21:12 -0500 [thread overview]
Message-ID: <4F6B5178.2040207@freescale.com> (raw)
In-Reply-To: <CALButC+gO1prxBhpKH=SKS+cVbN-vQqVN4tJUUTn3AfJf1SovA@mail.gmail.com>
On 03/21/2012 09:58 PM, Graeme Russ wrote:
> Hello Custodians and Mailing List Aficionados,
>
> I don't know if anyone has noticed, but patchwork is starting to collect
> a rather large amount of cruft.
>
> I occasionally jump onto patchwork and do a little housekeeping by marking
> updated patches as 'Superceeded' and anything applied by Wolfgang as
> 'Accepted' (There may be a few patches that have been applied to custodian
> tress that I marked as 'Accepted' when really they should have been marked
> as 'Awaiting Upstream')
>
> I really don't mind doing this housekeeping, but I would like to make a
> few suggestions that will make the work a little easier:
>
> - If you are a custodian:
> o When you apply a patch to your repo, can you please assign it to
> yourself in patchwork and set it to 'Awaiting Upstream'
> o Reply to the ML with 'Applied to <repo>/<branch>'
> o When you send a pull request, create a bundle with all the patches
> that are to be pulled (you can create the bundle early and add
> patches as you apply them)
> o When Wolfgang pulls your repo, go to the bundle and mark all the
> patches 'Accepted'
A while back I recall it being established that patches should be marked
"accepted" when they go into the custodian repo -- has this changed?
-Scott
next prev parent reply other threads:[~2012-03-22 16:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-22 2:58 [U-Boot] Patchwork housekeeping Graeme Russ
2012-03-22 6:45 ` Marek Vasut
2012-03-22 11:15 ` Graeme Russ
2012-03-22 11:35 ` Marek Vasut
2012-03-22 15:08 ` Tom Rini
2012-03-22 16:09 ` McClintock Matthew-B29882
2012-03-22 17:22 ` Tom Rini
2012-03-22 19:15 ` Khem Raj
2012-03-22 16:21 ` Scott Wood [this message]
2012-03-26 17:30 ` Vladimir Zapolskiy
2012-03-26 17:36 ` Andy Fleming
2012-03-26 17:49 ` Vladimir Zapolskiy
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=4F6B5178.2040207@freescale.com \
--to=scottwood@freescale.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.