public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Patchwork housekeeping
Date: Thu, 22 Mar 2012 08:08:42 -0700	[thread overview]
Message-ID: <4F6B407A.4010809@ti.com> (raw)
In-Reply-To: <CALButC+gO1prxBhpKH=SKS+cVbN-vQqVN4tJUUTn3AfJf1SovA@mail.gmail.com>

On 03/21/2012 07: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.

Do we, or do we not have the magic "update patchwork when the master 
repo gets a patch" hook setup?  It's not fool-proof, but it works well.

-- 
Tom

  parent reply	other threads:[~2012-03-22 15:08 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 [this message]
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
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=4F6B407A.4010809@ti.com \
    --to=trini@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox