From: Paul Jackson <pj@sgi.com>
To: Andrew Morton <akpm@osdl.org>
Cc: nagar@watson.ibm.com, jlan@sgi.com, Valdis.Kletnieks@vt.edu,
balbir@in.ibm.com, csturtiv@sgi.com,
linux-kernel@vger.kernel.org, hadi@cyberus.ca,
netdev@vger.kernel.org
Subject: Re: [PATCH] per-task delay accounting taskstats interface: control exit data through cpumasks]
Date: Thu, 6 Jul 2006 23:18:51 -0700 [thread overview]
Message-ID: <20060706231851.2f043927.pj@sgi.com> (raw)
In-Reply-To: <20060706025633.cd4b1c1d.akpm@osdl.org>
Andrew wrote:
> Your email client performs space-stuffing.
Shailabh,
Some of us find that it is easier and more reliable to use a special
purpose script to send patches, rather than trying to do so via our
email client. Even though my email client, Sylpheed, probably sends
patches just fine, I enjoy the convenience of preparing the patches
and mailing instructions in my editor, before sending them off with
such a utility.
One possible such utility is 'sendpatchset', which I maintain:
http://www.speakeasy.org/~pj99/sgi/sendpatchset
It's a script, with the documentation embedded as the help message.
Especially when sending off multiple patches as a set, it provides
more reliable results than trying to prepare and send multiple such
simultaneous messages from the typical email client.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.925.600.0401
prev parent reply other threads:[~2006-07-07 6:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-06 9:28 [PATCH] per-task delay accounting taskstats interface: control exit data through cpumasks] Shailabh Nagar
2006-07-06 9:56 ` Andrew Morton
2006-07-06 10:44 ` Shailabh Nagar
2006-07-06 11:37 ` Shailabh Nagar
2006-07-06 12:08 ` Thomas Graf
2006-07-06 13:21 ` Shailabh Nagar
2006-07-06 21:48 ` Andrew Morton
2006-07-06 22:27 ` Shailabh Nagar
2006-07-06 22:56 ` Andrew Morton
2006-07-07 10:21 ` Thomas Graf
2006-07-06 22:40 ` Thomas Graf
2006-07-06 23:05 ` Andrew Morton
2006-07-07 10:16 ` Thomas Graf
2006-07-07 6:18 ` Paul Jackson [this message]
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=20060706231851.2f043927.pj@sgi.com \
--to=pj@sgi.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@osdl.org \
--cc=balbir@in.ibm.com \
--cc=csturtiv@sgi.com \
--cc=hadi@cyberus.ca \
--cc=jlan@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nagar@watson.ibm.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).