From: Paul Jackson <pj@sgi.com>
To: Andrew Morton <akpm@osdl.org>
Cc: davidel@xmailserver.org, linux-kernel@vger.kernel.org
Subject: Re: [patch] Fix epoll delayed initialization bug ...
Date: Fri, 16 Sep 2005 19:37:41 -0700 [thread overview]
Message-ID: <20050916193741.74f5a830.pj@sgi.com> (raw)
In-Reply-To: <20050916165053.2dec0a6b.akpm@osdl.org>
Andrew complained:
> The number of whitespace-buggered patches which are coming in is just
> getting out of control lately.
If people didn't use email clients, but rather a patch sending script,
it would work better. It is easier to send patch sets this way (you get
to edit all the vital fields, such as Subject, To and Cc lists, in your
favorite text editor), and the usual failures that mess up patch
sending are avoided.
The script I'm using is in good shape, and several others besides
myself are successfully using it to send patches to lkml.
See the embedded Usage string for documentation.
http://www.speakeasy.org/~pj99/sgi/sendpatchset
It handles sending one or several related patches, to a list of email
addresses. You prepare a text directive file with the addresses,
subjects and pathnames to the files containing the message contents.
Then you send it all off with a single invocation of this 'sendpatchset'
script.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.925.600.0401
next prev parent reply other threads:[~2005-09-17 2:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-16 23:35 [patch] Fix epoll delayed initialization bug Davide Libenzi
2005-09-16 23:50 ` Andrew Morton
2005-09-16 23:56 ` Davide Libenzi
2005-09-17 0:05 ` Andrew Morton
2005-09-17 2:37 ` Paul Jackson [this message]
2005-09-16 23:59 ` Roland Dreier
2005-09-17 5:47 ` Al Viro
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=20050916193741.74f5a830.pj@sgi.com \
--to=pj@sgi.com \
--cc=akpm@osdl.org \
--cc=davidel@xmailserver.org \
--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