From: Paul Jackson <pj@sgi.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: michael-lists@free-electrons.com, rob@landley.net,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH] Documentation: mention email-clients.txt in SubmittingPatches
Date: Mon, 28 Jan 2008 15:48:27 -0600 [thread overview]
Message-ID: <20080128154827.fa97f04e.pj@sgi.com> (raw)
In-Reply-To: <479E4201.8040500@oracle.com>
> Agreed. I'll modify it.
Ok. Thanks.
No hurry; I probably shouldn't even
have worried about this in the first
place.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.940.382.4214
next prev parent reply other threads:[~2008-01-28 21:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-18 10:20 [PATCH] Documentation: mention email-clients.txt in SubmittingPatches Michael Opdenacker
2008-01-18 16:34 ` Randy Dunlap
2008-01-28 15:52 ` Paul Jackson
2008-01-28 16:17 ` Randy Dunlap
2008-01-28 19:32 ` Paul Jackson
2008-01-28 20:58 ` Randy Dunlap
2008-01-28 21:20 ` Randy Dunlap
2008-01-28 21:49 ` Paul Jackson
2008-01-28 21:48 ` Paul Jackson [this message]
2008-01-18 20:35 ` Jeff Garzik
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=20080128154827.fa97f04e.pj@sgi.com \
--to=pj@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael-lists@free-electrons.com \
--cc=randy.dunlap@oracle.com \
--cc=rob@landley.net \
/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