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

Re: Retroactively change email signature? [resend]

From
Sam Vilain <sam@vilain.net>
Date
Jan 4, 2008, 23:08 UTC
Message-ID
<477EBC7B.2080606@vilain.net>
In-Reply-To
<477EBB92.605@vilain.net>
Sam Vilain wrote:
Show 14 quoted lines
> Linus Torvalds wrote:
>> I don't care. If some commit refers to another commit that isn't its 
>> ancestor, then that is undefined *anyway*. 
>>
>> So the only case that really matters is when you refer to your own strict 
>> ancestor.
>>
>> This is one reason why it was so crazy that "git cherry-pick" used to have 
>> "-x" by default - appending the original SHA1 (which is generally *not* an 
>> ancestor) is meaningless and stupid.
> 
> Not stupid at all.  It gives you an easily clickable link to the
> previous version of the patch, which may be of interest, and is
> otherwise irretrievable information if the patch needed resolving.

footnote: of course it is entirely meaningless if the referred SHA1 is not published anywhere, so I agree with the cherry-pick default setting.

Sam.
Previous: Sam Vilain
Message 9 of 9 in “Retroactively change email signature?”
  1. Stephen SinclairJan 2, 2008
  2. Jakub NarebskiJan 2, 2008
  3. Linus TorvaldsJan 2, 2008
  4. Stephen SinclairJan 2, 2008
  5. David BrownJan 3, 2008
  6. Sam VilainJan 3, 2008
  7. Linus TorvaldsJan 4, 2008
  8. Sam VilainJan 4, 2008
  9. Sam VilainJan 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.