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

Why do we need [PATCH]?

From
Sam Ravnborg <sam@ravnborg.org>
Date
Dec 16, 2005, 21:01 UTC
Message-ID
<20051216210145.GA25311@mars.ravnborg.org>
Hi git's.

I've just applied a patch to my git tree using git-applymbox. It worked like a charm as it often do. But then when I did a quick check with gitk it stuck me that the subject was prefixed with [PATCH]. I am aware that the [PATCH] in subject tell me: "patch is received from somewhere and applied by me to the .git tree". This is in comparsion to patches received when I merge a git tree for example.

But with common practice to use sign-off I wonder the value of this
patch marker.
When browsing the kernel shortlog I often focus on first word in subject
- cause this tells me what system/drivers is changed. But with the
  [PATCH] marker I have to read some non-sense to see actual subject.

The information is redundant since metadata already tell me who is the author and who committed the change. So could we have it removed or if people continue to find it usefull then at least hide it behind some option. Using the [PATCH] prefix is not the natural thing to do with git.

I looked at the source and found the -k option, but adding [PATCH] should not be default behaviour so this is not the correct solution.

	Sam
Next: Dave Jones
Message 1 of 5 in “Why do we need [PATCH]?”
  1. Sam RavnborgDec 16, 2005
  2. Dave JonesDec 16, 2005
  3. Brian GerstDec 16, 2005
  4. Junio C HamanoDec 16, 2005
  5. Sam RavnborgDec 16, 2005

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.