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

Re: cannot find hash in the log output

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Dec 3, 2010, 20:29 UTC
Message-ID
<20101203202923.GB15517@burratino>
In-Reply-To
<AANLkTim59JP-fuVTeLwxV0bktbdCq04P8XzxVmbu2Qjd@mail.gmail.com>
Eugene Sajine wrote:
> Now as this is pretty much clear: don't you think that the information
> about one blob content changed during the merge should be present in
> the merge commit info?

"git rev-list <revs> | git diff-tree --root -c --stdin" might give some joy.

Previous: Eugene SajineNext: Eugene Sajine
Message 7 of 14 in “cannot find hash in the log output”
  1. Eugene SajineDec 2, 2010
  2. Junio C HamanoDec 2, 2010
  3. Eugene SajineDec 2, 2010
  4. Eugene SajineDec 3, 2010
  5. Jeff KingDec 3, 2010
  6. Eugene SajineDec 3, 2010
  7. Jonathan NiederDec 3, 2010
  8. Eugene SajineDec 3, 2010
  9. Jonathan NiederDec 3, 2010
  10. Eugene SajineDec 3, 2010
  11. Junio C HamanoDec 3, 2010
  12. Jonathan NiederDec 4, 2010
  13. Jeff KingDec 3, 2010
  14. Jeff KingDec 3, 2010

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.