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

Re: Could we please make "cherry-pick" not add the message by default?

From
Junio C Hamano <junkio@cox.net>
Date
Oct 6, 2006, 00:35 UTC
Message-ID
<7v1wpm5lih.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<Pine.LNX.4.64.0610051711310.3952@g5.osdl.org>
Linus Torvalds <torvalds@osdl.org> writes:
Show 15 quoted lines
> It appears that more and more people are finding "git cherry-pick", and we 
> now have a number of totally inane
>
> 	cherry picked from 1b16e7ac850969f38b375e511e3fa2f474a33867 commit
>
> messages in the kernel logs, because I don't want to just re-cherry-pick 
> them and edit peoples logs.
>
> Those messages not only make no grammatical sense (you'd say "commit X" 
> rather than "X commit"), but they have no point. The original commit is 
> not reachable and makes no sense any more, and that's actually likely to 
> always be the common case.
>
> So could we just (a) fix the message word order to make sense and (b) make 
> it only happen if people explicitly ask for it, rather than by default?
Let's do (c) never show it and make -r a no-op.
Previous: Linus TorvaldsNext: Junio C Hamano
Message 2 of 4 in “Could we please make "cherry-pick" not add the message by default?”
  1. Linus TorvaldsOct 6, 2006
  2. Junio C HamanoOct 6, 2006
  3. cherry-pick: make -r the defaultJunio C Hamano, Oct 6, 2006
  4. Linus TorvaldsOct 6, 2006

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.