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

Re: [PATCH 2/2] Add submitGit patch-submission information

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 14, 2016, 23:03 UTC
Message-ID
<xmqqpotreqso.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<xmqq37qng721.fsf@gitster.mtv.corp.google.com>
Junio C Hamano <gitster@pobox.com> writes:
Show 10 quoted lines
>> +Because of these factors, it's recommended that you use one of these
>> +specific methods to generate and send your patchs:
>
> Perhaps:
>
>     It's recommended ... your patches, unless you already know how
>     to correctly send your patches as plain-text e-mails.
>
> That is, the ones listed below are known to produce good patches,
> but our recommendation is _so_ strong to urge users with working
Well, I meant "our recommendation is *not* so strong" here.
Previous: Junio C HamanoNext: Jeff King
Message 4 of 6 in “Partition SubmittingPatches doc into two files”
  1. 1/2 Partition SubmittingPatches doc into two filesRoberto Tyley, Apr 14, 2016
  2. 2/2 Add submitGit patch-submission informationRoberto Tyley, Apr 14, 2016
  3. Junio C HamanoApr 14, 2016
  4. Junio C HamanoApr 14, 2016
  5. Jeff KingApr 15, 2016
  6. Junio C HamanoApr 14, 2016

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.