Re: pack v4 trees with a canonical base

On Tue, 10 Sep 2013, Junio C Hamano wrote: > Nicolas Pitre writes: > > > On Tue, 10 Sep 2013, Junio C Hamano wrote: > > > >> There may be trees in the wild that record 100775 or 100777 in the > >> mode field for executable blobs, which also need to be special > >> cased. > > > > All the file mod

Re: pack v4 trees with a canonical base

Nicolas Pitre writes: very much appreciated to> On Tue, 10 Sep 2013, Junio C Hamano wrote: > >> Duy Nguyen writes: >> >> > On Tue, Sep 10, 2013 at 2:25 AM, Nicolas Pitre wrote: >> >> An eventual optimization to index-pack when completing a pack would be >> >> to attempt the encoding of appende

Re: pack v4 trees with a canonical base

On Tue, 10 Sep 2013, Junio C Hamano wrote: > Duy Nguyen writes: > > > On Tue, Sep 10, 2013 at 2:25 AM, Nicolas Pitre wrote: > >> An eventual optimization to index-pack when completing a pack would be > >> to attempt the encoding of appended tree objects into the packv4 format > >> using the exi

Re: pack v4 trees with a canonical base

Duy Nguyen writes: > On Tue, Sep 10, 2013 at 2:25 AM, Nicolas Pitre wrote: >> An eventual optimization to index-pack when completing a pack would be >> to attempt the encoding of appended tree objects into the packv4 format >> using the existing dictionary table in the pack, and fall back to the

Re: pack v4 trees with a canonical base

On Tue, Sep 10, 2013 at 2:25 AM, Nicolas Pitre wrote: > An eventual optimization to index-pack when completing a pack would be > to attempt the encoding of appended tree objects into the packv4 format > using the existing dictionary table in the pack, and fall back to the > canonical format if tha

pack v4 trees with a canonical base

While reviewing the pack v4 thin support Ive realized that some base tree objects appended to a thin pack won't be in pack v4 format. Hence the patch below to deal with that possibility. An eventual optimization to index-pack when completing a pack would be to attempt the encoding of appended