Re: Rebase max-pack-size?

"Dana How" [off-list ref] writes:

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.

quoted

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).