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

Re: [PATCH] Documentation/SubmittingPatches: Instruct how to use [PATCH] Subject header

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Feb 4, 2008, 00:29 UTC
Message-ID
<alpine.LSU.1.00.0802040029020.7372@racer.site>
In-Reply-To
<r6ft1sd1.fsf@blue.sea.net>
Hi,
On Mon, 4 Feb 2008, Jari Aalto wrote:
Show 7 quoted lines
> @@ -37,6 +37,9 @@ Checklist (and a short version for the impatient):
>  	  maintainer (gitster@pobox.com). If you use
>  	  git-send-email(1), please test it first by sending
>  	  email to yourself.
> +        - If you rework the patch, announce the message
> +          in brackets. For example "[PATCH/RFC]", "[PATCH (resend)]",
> +          "[PATCH v2]" etc.
Whitespace error?  (Spaces instead of Tabs)

Ciao, Dscho

Previous: Jari AaltoNext: Jari Aalto
Message 2 of 6 in “Documentation/SubmittingPatches: Instruct how to use [PATCH] Subject header”
  1. Documentation/SubmittingPatches: Instruct how to use [PATCH] Subject headerJari Aalto, Feb 4, 2008
  2. Johannes SchindelinFeb 4, 2008
  3. Jari AaltoFeb 4, 2008
  4. Junio C HamanoFeb 4, 2008
  5. 1/2 Documentation/SubmittingPatches: discuss first then submitJunio C Hamano, Feb 4, 2008
  6. 2/2 Documentation/SubmittingPatches: What's Acked-by and Tested-by?Junio C Hamano, Feb 4, 2008

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.