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

Re: [PATCH] Documentation: add KMail in SubmittingPatches

From
Junio C Hamano <junkio@cox.net>
Date
Feb 6, 2007, 03:07 UTC
Message-ID
<7vveigkmpv.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<200702051427.32532.barra_cuda@katamail.com>
Michael <barra_cuda@katamail.com> writes:
Show 23 quoted lines
> @@ -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.
> +
This is quite interesting -- notice your own hunk header @@ ... @@ line?

I do not use KMail myself, so I cannot comment on the procedure, but from the cursory look it *should* do the right thing. Only that it makes me a bit nervous to see your hunk header being line wrapped.

Doubly interesting is that somebody appears to have added two message IDs.

   Subject: [PATCH] Documentation: add KMail in SubmittingPatches
   Date:	Mon, 5 Feb 2007 14:27:32 +0100
   User-Agent: KMail/1.9.4
   Message-Id: <200702051427.32532.barra_cuda@katamail.com>
   Message-ID: <20070205132150.123659@dial-up-mi-449.lombardiacom.it>
Previous: MichaelNext: Michael
Message 9 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.