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

Re: linux-next: unneeded merge in the security tree

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 12, 2013, 22:00 UTC
Message-ID
<7vli9s5ldz.fsf@alter.siamese.dyndns.org>
In-Reply-To
<CA+55aFzWjfFjcRZXBO+edO7f66REA0pOsC3iZ2vYdHrkcovnHA@mail.gmail.com>
Linus Torvalds <torvalds@linux-foundation.org> writes:
> That said, adding the signature from an upstream tag doesn't really
> seem to be hugely useful. I'm not seeing much of an upside, in other
> words. I'd *expect* that people would pick up upstream tags
> regardless, no?

Yes, their "git fetch" will auto-follow, but mergetag embedded in the commit objects will give the history auditable trail the same way as the merges you make your downstream. You of course could match out-of-line tags against back-merges and verify your merges with mergetags, but you do not have to.

Previous: Linus TorvaldsNext: Junio C Hamano
Message 9 of 12 in “Re: linux-next: unneeded merge in the security tree”
  1. Linus TorvaldsMar 12, 2013
  2. Geert UytterhoevenMar 12, 2013
  3. Junio C HamanoMar 12, 2013
  4. Junio C HamanoMar 12, 2013
  5. Theodore Ts'oMar 12, 2013
  6. Linus TorvaldsMar 12, 2013
  7. Junio C HamanoMar 12, 2013
  8. Linus TorvaldsMar 12, 2013
  9. Junio C HamanoMar 12, 2013
  10. Junio C HamanoMar 12, 2013
  11. Theodore Ts'oMar 13, 2013
  12. Junio C HamanoMar 13, 2013

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.