aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMichael <barra_cuda@katamail.com>2007-02-05 14:27:32 +0100
committerJunio C Hamano <junkio@cox.net>2007-02-07 00:33:38 -0800
commit451fd65a8ebb8c91fbceac3be705b274aa3e3673 (patch)
tree4b3835970d27a1bb6d98a5304af7d80cbde1433d
parent6506e156d99bd406661cd5d2e502db7c0960d716 (diff)
downloadgit-451fd65a8ebb8c91fbceac3be705b274aa3e3673.tar.gz
git-451fd65a8ebb8c91fbceac3be705b274aa3e3673.tar.xz
Documentation: add KMail in SubmittingPatches
Signed-off-by: Michael <barra_cuda@katamail.com> Signed-off-by: Junio C Hamano <junkio@cox.net>
-rw-r--r--Documentation/SubmittingPatches18
1 files changed, 17 insertions, 1 deletions
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index ce85d06c6..285781d9d 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,20 @@ 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.