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

Re: [PATCH] Documentation: git-format-patch.txt rewordings and cleanups

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 24, 2009, 23:55 UTC
Message-ID
<7vskl2tr00.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<780e0a6b0903241636j4749daf3xddb6e4c200c00820@mail.gmail.com>
Stephen Boyd <bebarino@gmail.com> writes:
> How about a sentence with no negation?
>
> "Note that the leading dot is required if you want a dot between the
> patch name and the suffix."
How about a sentence that does not sound requirement but freedom?

"The leading character does not have to be a dot; for example, you can use --suffix=-patch to get 0001-description-of-my-change-patch".

Previous: J. Bruce FieldsNext: Stephen Boyd
Message 5 of 7 in “Documentation: git-format-patch.txt rewordings and cleanups”
  1. Documentation: git-format-patch.txt rewordings and cleanupsStephen Boyd, Mar 23, 2009
  2. J. Bruce FieldsMar 24, 2009
  3. Stephen BoydMar 24, 2009
  4. J. Bruce FieldsMar 24, 2009
  5. Junio C HamanoMar 24, 2009
  6. Stephen BoydMar 25, 2009
  7. Junio C HamanoMar 25, 2009

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.