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

Re: Sending patches with KMail

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Jan 14, 2012, 18:31 UTC
Message-ID
<20120114183111.GC27850@burratino>
In-Reply-To
<7vlipbxfne.fsf@alter.siamese.dyndns.org>
Junio C Hamano wrote:
> Jonathan Nieder <jrnieder@gmail.com> writes:
>> The hints at [1] might also be useful, in case you would like to try
>> and consider improving the manpage to document them if they work.
>
> Don't you need similar updates to sections for other MUAs and procedures?
Thunderbird approach 3, yes[*].  The others, no.
[...]
> Perhaps rephrasing the early part of the Discussion section, with an
> illustration that is designed to be more visible, would be a better
> approach?

I understand what you mean, but I don't think so. The Discussion section already seems clear to me, so I would prefer to wait to hear from someone confused by it to find what exactly in it needs tweaking. Adding additional paragraphs for each potential misunderstanding by people who have not necessarily read the section has the potential to backfire and lead even more people not to read the section...

My favorite approach would be to introduce a new option --format=plain|mbox, with the default being mbox, allowing format-patch --format=plain to produce a nice patch that does _not_ include a "From " line or q-encode its header lines, ready for use without much tweaking in an email body as an attachment. Then we can just say "If you are not importing your patch as an mbox file, use the --format=plain option".

Sane?
Jonathan

[*] Though I'd rather just remove it, since "how to use an external editor" seems orthogonal to "how to teach Thunderbird not to mangle my patches".

Previous: Junio C HamanoNext: Jonathan Nieder
Message 6 of 18 in “git-blame.el: Fix compilation warnings.”
  1. git-blame.el: Fix compilation warnings.Rüdiger Sonderfeld, Jan 12, 2012
  2. Jonathan NiederJan 12, 2012
  3. Rüdiger SonderfeldJan 12, 2012
  4. Sending patches with KMail (Re: [PATCH] git-blame.el: Fix compilation warnings.)Jonathan Nieder, Jan 13, 2012
  5. Junio C HamanoJan 14, 2012
  6. Jonathan NiederJan 14, 2012
  7. Jonathan NiederJan 14, 2012
  8. Junio C HamanoJan 15, 2012
  9. Rüdiger SonderfeldJan 14, 2012
  10. git-blame.el: use mapc instead of mapcarJonathan Nieder, Jun 10, 2012
  11. 1/3 git-blame.el: Do not use goto-line in lisp codeLawrence Mitchell, Jun 10, 2012
  12. 2/3 git-blame.el: Use with-current-buffer where appropriateLawrence Mitchell, Jun 10, 2012
  13. 3/3 git-blame.el: Do not use bare 0 to mean (point-min)Lawrence Mitchell, Jun 10, 2012
  14. Jonathan NiederJun 14, 2012
  15. Lawrence MitchellJun 14, 2012
  16. 1/3 git-blame.el: Do not use goto-line in lisp codeLawrence Mitchell, Jun 14, 2012
  17. 2/3 git-blame.el: Use with-current-buffer where appropriateLawrence Mitchell, Jun 14, 2012
  18. 3/3 git-blame.el: Do not use bare 0 to mean (point-min)Lawrence Mitchell, Jun 14, 2012

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.