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

Re: [RFC/PATCH 1/2] commit: add parse_commit_repl() to replace commits at parsing time

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Aug 18, 2010, 04:24 UTC
Message-ID
<20100818042459.GD21185@burratino>
In-Reply-To
<201008180607.54675.chriscool@tuxfamily.org>
Christian Couder wrote:
> The downside is that the sha1 will not be 
> consistent with the content anymore and that it will be more difficult to 
> realize that an object has been replaced as there will be no sha1 change to be 
> seen.

Maybe in the long run it would make sense to keep a "replaced" flag and use it to mark the replace objects specially in some user-facing commands (like log --format=medium).

Previous: Christian CouderNext: Nguyen Thai Ngoc Duy
Message 5 of 8 in “commit: add parse_commit_repl() to replace commits at parsing time”
  1. 1/2 commit: add parse_commit_repl() to replace commits at parsing timeChristian Couder, Aug 17, 2010
  2. Junio C HamanoAug 17, 2010
  3. Nguyen Thai Ngoc DuyAug 18, 2010
  4. Christian CouderAug 18, 2010
  5. Jonathan NiederAug 18, 2010
  6. Nguyen Thai Ngoc DuyAug 18, 2010
  7. Junio C HamanoAug 18, 2010
  8. Christian CouderAug 20, 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.