public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4] Add 'patman' patch generation, checking and submission script
Date: Fri, 03 Feb 2012 20:00:11 +0100	[thread overview]
Message-ID: <4F2C2EBB.40203@aribaud.net> (raw)
In-Reply-To: <CAPnjgZ2TZKPwN4fBztzQYoyPKQNp57v5uZwxYTC_bU+_qA=7ww@mail.gmail.com>

Hi Simon,

Le 15/01/2012 02:20, Simon Glass a ?crit :
> Hi,
>
> Hmmm patman found a tag in this commit and tried to send it to Fred
> Bloggs. I have added the line below - sorry for the confusion.
>
> On Sat, Jan 14, 2012 at 5:12 PM, Simon Glass<sjg@chromium.org>  wrote:
>> What is this?
>> =============
>>
>> This tool is a Python script which:
>> - Creates patch directly from your branch
>> - Cleans them up by removing unwanted tags
>> - Inserts a cover letter with change lists
>> - Runs the patches through checkpatch.pl and its own checks
>> - Optionally emails them out to selected people

It seems to me that this is not specific to u-boot, and as such, has no 
reason to be managed along with U-Boot.

Why should it not simply have its own project and resources?

Amicalement,
-- 
Albert.

  reply	other threads:[~2012-02-03 19:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-15  1:12 [U-Boot] [PATCH v4] Add 'patman' patch generation, checking and submission script Simon Glass
2012-01-15  1:20 ` Simon Glass
2012-02-03 19:00   ` Albert ARIBAUD [this message]
2012-02-03 19:30     ` Simon Glass
2012-02-03 20:00       ` Albert ARIBAUD
2012-02-05  5:46         ` Simon Glass
2012-02-12 13:55           ` Albert ARIBAUD
2012-04-04 10:35 ` Gerlando Falauto
2012-04-04 16:16   ` Simon Glass
2012-04-04 16:38     ` Gerlando Falauto
2012-04-04 16:43       ` Simon Glass
2012-04-21 15:26 ` Wolfgang Denk

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=4F2C2EBB.40203@aribaud.net \
    --to=albert.u.boot@aribaud.net \
    --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