From: Michael <barra_cuda@katamail.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <junkio@cox.net>,
Robin Rosenberg <robin.rosenberg.lists@dewire.com>
Subject: [PATCH] Documentation: add KMail in SubmittingPatches
Date: Mon, 5 Feb 2007 14:27:32 +0100 [thread overview]
Message-ID: <200702051427.32532.barra_cuda@katamail.com> (raw)
Message-ID: <20070205132150.123659@dial-up-mi-449.lombardiacom.it> (raw)
In-Reply-To: <7vlkjdr8hj.fsf@assigned-by-dhcp.cox.net>
Signed-off-by: Michael <barra_cuda@katamail.com>
---
Documentation/SubmittingPatches | 19 ++++++++++++++++++-
1 files changed, 18 insertions(+), 1 deletions(-)
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index ce85d06..a3dafa5 100644
--- a/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches
@@ -316,7 +316,6 @@ settings but I haven't tried, yet.
mail.identity.id?.compose_html => false
-
Gnus
----
@@ -331,3 +330,21 @@ whitespaces (fatal in patches). Running 'C-u g' to
display the
message in raw form before using '|' to run the pipe can work
this problem around.
+
+KMail
+-----
+
+This should help you to submit patches inline using KMail.
+
+1) Prepare the patch as a text file.
+
+2) Click on New Mail.
+
+3) Go under "Options" in the Composer window and be sure that
+"Word wrap" is not set.
+
+4) Use Message -> Insert file... and insert the patch.
+
+5) Back in the compose window: add whatever other text you wish to the
+message, complete the addressing and subject fields, and press send.
+
--
1.4.4.2
next prev parent reply other threads:[~2007-02-05 13:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-03 6:40 Why is it bad to rewind a branch that has already been pushed out? Junio C Hamano
2007-02-03 10:40 ` Andy Parkins
2007-02-03 19:42 ` Junio C Hamano
2007-02-04 18:01 ` Andy Parkins
2007-02-03 13:20 ` Theodore Tso
2007-02-04 16:16 ` Robin Rosenberg
2007-02-04 20:08 ` Junio C Hamano
[not found] ` <20070205132150.123659@dial-up-mi-449.lombardiacom.it>
2007-02-05 13:27 ` Michael [this message]
2007-02-06 3:07 ` [PATCH] Documentation: add KMail in SubmittingPatches Junio C Hamano
2007-02-06 13:45 ` Michael
2007-02-06 14:16 ` Jakub Narebski
2007-02-06 14:47 ` Andy Parkins
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=200702051427.32532.barra_cuda@katamail.com \
--to=barra_cuda@katamail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=robin.rosenberg.lists@dewire.com \
/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).