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

Re: Rebase max-pack-size?

From
Junio C Hamano <junkio@cox.net>
Date
May 23, 2007, 07:23 UTC
Message-ID
<7vodkc3swx.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<56b7f5510705222333l6e285e67l1dc327322a2ab250@mail.gmail.com>
"Dana How" <danahow@gmail.com> writes:
Show 15 quoted lines
> Patch 1:
> * Pull "sha1flush()" or similar out of sha1close() inside csum-file.c.
>  This will require some edits to callers.
>
> Patch 2:
> * Add a comment to "confusing loop" to explain what it's checking.
> * Complain about --stdout && --max-pack-size combination.
>
> This will have to happen tomorrow.
>
>> And I have to agree with Linus; responding this way was more
>> cumbersome than it should have been.
> Understood.
>
> Thanks,

Although I mentioned it, as we have only one caller that does not want to close the file, we probably do not need the first patch right now.

Also thanks for the clarification on the (nr_result != nr_objects) stuff -- it should have been obvious, as I was the guilty party who originally introduced that condition (i.e. "thin" packs).

Previous: Dana How
Message 4 of 4 in “Re: Rebase max-pack-size?”
  1. Dana HowMay 14, 2007
  2. Junio C HamanoMay 23, 2007
  3. Dana HowMay 23, 2007
  4. Junio C HamanoMay 23, 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.