git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH] Documentation: add KMail in SubmittingPatches

From
Michael <barra_cuda@katamail.com>
Date
Feb 5, 2007, 13:27 UTC
Message-ID
<200702051427.32532.barra_cuda@katamail.com>
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
Previous: Junio C HamanoNext: Junio C Hamano
Message 8 of 12 in “Why is it bad to rewind a branch that has already been pushed out?”
  1. Junio C HamanoFeb 3, 2007
  2. Andy ParkinsFeb 3, 2007
  3. Junio C HamanoFeb 3, 2007
  4. Andy ParkinsFeb 4, 2007
  5. Theodore TsoFeb 3, 2007
  6. Robin RosenbergFeb 4, 2007
  7. Junio C HamanoFeb 4, 2007
  8. Documentation: add KMail in SubmittingPatchesMichael, Feb 5, 2007
  9. Junio C HamanoFeb 6, 2007
  10. MichaelFeb 6, 2007
  11. Jakub NarebskiFeb 6, 2007
  12. Andy ParkinsFeb 6, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.