From: Richard Weinberger <richard@nod.at>
To: Simon Glass <sjg@chromium.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Doug Anderson <dianders@chromium.org>
Subject: Re: [PATCH 1/3] Add patman patch automation script
Date: Sun, 03 May 2015 22:13:54 +0200 [thread overview]
Message-ID: <55468182.3030706@nod.at> (raw)
In-Reply-To: <CAPnjgZ0=-C++dC7Coet+Gc-a8yZg9TjF9Eypm-5dVnxYwzdqAw@mail.gmail.com>
Simon,
Am 03.05.2015 um 21:54 schrieb Simon Glass:
> Hi Richard,
>
> On 3 May 2015 at 13:16, Richard Weinberger <richard.weinberger@gmail.com> wrote:
>> On Sun, May 3, 2015 at 8:29 PM, Simon Glass <sjg@chromium.org> wrote:
>>> 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
>>
>> Don't get me wrong but is this really worth 3000+ lines of python?
>> The tasks you describe can be done using a few lines bash.
>
> #!/bin/bash
> patman $@
>
> I obviously failed in my attempt to briefly explain what it does.
> Please check out the cover letter [1], README [2], or perhaps use it
> on a series. With respect to the length, it could be slimmed down a
> bit if that is important.
the README file did the trick. ;)
Sounds like a useful tool to manage patch series.
But I don't think it makes much sense to carry it with the Linux kernel tree.
Other projects can also use it and it does not seem to be very Linux kernel
specific.
git, quilt and other great tools also have their own repositories.
Thanks,
//richard
next prev parent reply other threads:[~2015-05-03 20:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-03 18:29 [PATCH 0/3] Add a tool to simplify patch checking and posting (patman) Simon Glass
2015-05-03 18:29 ` [PATCH 1/3] Add patman patch automation script Simon Glass
2015-05-03 19:16 ` Richard Weinberger
2015-05-03 19:54 ` Simon Glass
2015-05-03 20:13 ` Richard Weinberger [this message]
2015-05-03 20:40 ` Simon Glass
2015-05-03 20:43 ` Richard Weinberger
2015-05-03 21:43 ` Simon Glass
2015-05-03 18:29 ` [PATCH 2/3] Add tests for patman Simon Glass
2015-05-03 18:29 ` [PATCH 3/3] Add documentation " Simon Glass
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=55468182.3030706@nod.at \
--to=richard@nod.at \
--cc=dianders@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sjg@chromium.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