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

Re: Recording merges after repo conversion

From
Peter Karlsson <peter@softwolves.pp.se>
Date
Oct 31, 2007, 09:50 UTC
Message-ID
<Pine.LNX.4.62.0710311048450.13264@perkele.intern.softwolves.pp.se>
In-Reply-To
<Pine.LNX.4.64.0710310227340.4362@racer.site>
Johannes Schindelin:
> Why should it?  This would contradict the whole "a commit sha1 hashes the
> commit, and by inference the _whole_ history" principle.

Does it? Why can't the grafts file itself be committed to the repository and live in the history?

Well, yeah, the SHA1 hashing is one of Git's main strengths, but it also opens up some weaknesses.

-- 
\\// Peter - http://www.softwolves.pp.se/
Previous: Johannes SchindelinNext: Johannes Schindelin
Message 8 of 21 in “Recording merges after repo conversion”
  1. Peter KarlssonOct 9, 2007
  2. Benoit SIGOUREOct 9, 2007
  3. Peter KarlssonOct 30, 2007
  4. Lars HjemliOct 30, 2007
  5. Peter KarlssonOct 30, 2007
  6. Lars HjemliOct 30, 2007
  7. Johannes SchindelinOct 31, 2007
  8. Peter KarlssonOct 31, 2007
  9. Johannes SchindelinOct 31, 2007
  10. Peter KarlssonOct 31, 2007
  11. Johannes SchindelinOct 31, 2007
  12. Johan HerlandOct 31, 2007
  13. Johannes SchindelinOct 31, 2007
  14. Johan HerlandOct 31, 2007
  15. Johannes SchindelinOct 31, 2007
  16. Johan HerlandOct 31, 2007
  17. Johannes SchindelinOct 31, 2007
  18. Linus TorvaldsOct 31, 2007
  19. Johan HerlandOct 31, 2007
  20. Johannes SchindelinOct 30, 2007
  21. Peter KarlssonOct 31, 2007

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.