public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Michael Opdenacker <michael-lists@free-electrons.com>
Cc: rob@landley.net, linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] Documentation: mention email-clients.txt in SubmittingPatches
Date: Fri, 18 Jan 2008 15:35:50 -0500	[thread overview]
Message-ID: <47910DA6.8070905@garzik.org> (raw)
In-Reply-To: <200801181120.03168.michael-lists@free-electrons.com>

Michael Opdenacker wrote:
> Applies to 2.6.24-rc8-git2
> 
> I was struggling to get my email-client no to mangle my patch files,
> and I didn't find enough information in the SubmittingPatches file.
> By looking for more information on the web, I eventually found the
> email-clients.txt file, and it answered all my needs
> 
> This patch adds a reference to email-clients.txt in SubmittingPatches,
> and Mozilla related information which is no longer accurate
> (as opposed to the details found in email-clients.txt).
> 
> This should be helpful for people sending their first patches,
> or not sending patches on a frequent basis.
> 
> Michael.
> 
> --
> Signed-off-by: Michael Opdenacker <michael@free-electrons.com>

ACK


      parent reply	other threads:[~2008-01-18 20:36 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
2008-01-18 20:35 ` Jeff Garzik [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=47910DA6.8070905@garzik.org \
    --to=jeff@garzik.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael-lists@free-electrons.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