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

Re: [PATCH] remove doubled words, e.g., s/to to/to/, and fix related typos

From
Jim Meyering <jim@meyering.net>
Date
Apr 13, 2011, 21:22 UTC
Message-ID
<87mxjtn8x7.fsf@rho.meyering.net>
In-Reply-To
<1302719749.21047.6.camel@drew-northup.unet.maine.edu>
Drew Northup wrote:
Show 12 quoted lines
> On Wed, 2011-04-13 at 17:39 +0200, Jim Meyering wrote:
>> I found that some doubled words had snuck back into projects from
>> which I'd already removed them, so now there's a "syntax-check" makefile
>> rule in gnulib to help prevent recurrence.  Running the command below
>> spotted a few in git, too:
>>
>> This patch is relative to "next".
>
> Jim,
> Try putting the output of git format-patch into your drafts folder, then
> open that draft in your mail client. The output of format-patch isn't
> meant to be pasted directly into a mail message.

I hope I haven't caused Junio or anyone else undue trouble. I know well how format-patch output can be used, but in the vast majority of patch-including messages I send, I include format-patch output mainly as an FYI, *following* commentary that does not belong in the log, so it's ok there -- desirable, even.

I find it slightly backwards to have to put non-log (i.e, intro commentary) *after* the real log, and that's why I've developed this habit.

I'll try to remember to do it the other way when the recipient is more likely to apply the patch.

Previous: Drew NorthupNext: Jonathan Nieder
Message 3 of 26 in “remove doubled words, e.g., s/to to/to/, and fix related typos”
  1. remove doubled words, e.g., s/to to/to/, and fix related typosJim Meyering, Apr 13, 2011
  2. Drew NorthupApr 13, 2011
  3. Jim MeyeringApr 13, 2011
  4. Documentation/format-patch: summarize patch-sending workflowJonathan Nieder, Apr 13, 2011
  5. Junio C HamanoApr 13, 2011
  6. Documentation: summarize how format-patch output is consumedJonathan Nieder, Apr 14, 2011
  7. Junio C HamanoApr 14, 2011
  8. 0/5 Documentation/format-patch: more hints on submitting patchesJonathan Nieder, Apr 15, 2011
  9. 1/5 Documentation: describe the format of messages with inline patchesJonathan Nieder, Apr 15, 2011
  10. Drew NorthupApr 15, 2011
  11. Junio C HamanoApr 15, 2011
  12. 2/5 Documentation: explain how to check for patch corruptionJonathan Nieder, Apr 15, 2011
  13. Junio C HamanoApr 15, 2011
  14. Jonathan NiederApr 15, 2011
  15. 3/5 Documentation: hints for sending patches inline with ThunderbirdJonathan Nieder, Apr 15, 2011
  16. 4/5 Documentation: publicize KMail hints for sending patches inlineJonathan Nieder, Apr 15, 2011
  17. Michele BallabioApr 17, 2011
  18. 5/5 Documentation: publicize hints for sending patches with GMailJonathan Nieder, Apr 15, 2011
  19. 6/5 Documentation/format-patch: suggest Toggle Word Wrap add-on for ThunderbirdJohannes Sixt, Apr 15, 2011
  20. Junio C HamanoApr 15, 2011
  21. Michael J GruberApr 15, 2011
  22. Junio C HamanoApr 15, 2011
  23. Jonathan NiederApr 15, 2011
  24. 6/5 Documentation/format-patch: suggest Toggle Word Wrap add-on for ThunderbirdJohannes Sixt, Apr 18, 2011
  25. Jakub NarebskiApr 13, 2011
  26. Junio C HamanoApr 13, 2011

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.