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

Re: [PATCH] parse_object: pass on the original sha1, not the replaced one

From
Christian Couder <chriscool@tuxfamily.org>
Date
Sep 3, 2010, 04:37 UTC
Message-ID
<201009030637.41728.chriscool@tuxfamily.org>
In-Reply-To
<AANLkTikBau2-ggvZa2Zp35gTk_j8JEAY8nyVh3i0-ap7@mail.gmail.com>
On Friday 03 September 2010 01:24:07 Nguyen Thai Ngoc Duy wrote:
Show 9 quoted lines
> On Fri, Sep 3, 2010 at 7:13 AM, Christian Couder
> 
> <chriscool@tuxfamily.org> wrote:
> > Since no one resent the original patch with an improved commit
> > message, here is my try.
> 
> My bad. I forgot something again. I will think of something to
> demonstrate this. By the way, it breaks t6050.14, bisect and
> replacements.
Ooops, yeah, I will have a look at this.

Thanks, Christian.

Previous: Nguyen Thai Ngoc Duy
Message 3 of 3 in “parse_object: pass on the original sha1, not the replaced one”
  1. parse_object: pass on the original sha1, not the replaced oneChristian Couder, Sep 2, 2010
  2. Nguyen Thai Ngoc DuySep 2, 2010
  3. Christian CouderSep 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.