Re: [PATCH 5/8] get-repack --max-pack-size: write_object() takes 'limit' arg
- From
Nicolas Pitre <nico@cam.org>
- Date
- Apr 9, 2007, 02:28 UTC
- Message-ID
- <alpine.LFD.0.98.0704082227580.28181@xanadu.home>
- In-Reply-To
- <7vr6qu768r.fsf@assigned-by-dhcp.cox.net>
On Sun, 8 Apr 2007, Junio C Hamano wrote:
Show 21 quoted lines
> Junio C Hamano <junkio@cox.net> writes: > > > Dana How <danahow@gmail.com> writes: > > > >> Accept new 'limit' argument and check against it > >> before each group of writes. Update delta usability rules > >> for possibility of delta base being in a previously- > >> written pack. Inline sha1write_compressed() so we know > >> the exact size of the written data when it needs to be compressed. > >> > >> Signed-off-by: Dana How <how@deathvalley.cswitch.com> > > > > My first reaction of open-coding sha1write_compressed() was > > "Ugh", but as you are removing the only user of that function, > > maybe this is not as bad as it looks. > > Having said that, I suspect that for other possible users of > that function we might have later, it would be a better > interface to add an optional 'limit' and 'prelude' to > sha1write_compressed(). The function would write prelude > followed by the compressed payload, only if they fit the limit.
I'd wait for those possible future users to show up before doing such thing though.
Nicolas