public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: lkml <linux-kernel@vger.kernel.org>
Subject: [UTILITY] lksp - Help sending patches to lkml from quilt repository
Date: Fri, 11 Feb 2005 16:31:11 +0900	[thread overview]
Message-ID: <420C5F3F.9060105@gmail.com> (raw)


 Hello,

 As I've been making quite a few mistakes posting patches to lkml.  I
wrote a perl script which automates sending multiple patches to lkml
from a quilt repository.

 lksp can...

 1. generate template index message.
 2. use only specified range of patches from the quilt repository.
 3. use the edited index message to generate individual patch mail
messages combined with patches acquired from quilt.
 4. keep all patch descriptions you wrote and reuse them.
 5. let you blame the script if something goes wrong and you end up
polluting other people's inbox.

 More information on lksp can be found at
 http://home-tj.org/lksp

 And the script can be downloaded from
 http://home-tj.org/lksp/files/lksp-0.1

 If you've found bugs or have any ideas, please let me know.

 Hope it helps. :-)

-- 
tejun


                 reply	other threads:[~2005-02-11  7:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=420C5F3F.9060105@gmail.com \
    --to=htejun@gmail.com \
    --cc=linux-kernel@vger.kernel.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