"Dana How" [off-list ref] writes:
... But such an attribute should be
ignored when --stdout is in effect -- it only affects on-disk
repacking, not packing for transfers, which is why it's named "repack".
Yes -- if we want to have an option to keep objects selectively
left out of packs in loose format, you would need 'repack' which
acts differently between the server-feeding-client case vs
packing-repository case.
Which is a bigger change that I did not want to show in the
quick-and-clean patch, but I would agree we would want both.
On 5/19/07, Junio C Hamano [off-list ref] wrote:
"Dana How" [off-list ref] writes:
quoted
... But such an attribute should be
ignored when --stdout is in effect -- it only affects on-disk
repacking, not packing for transfers, which is why it's named "repack".
Yes -- if we want to have an option to keep objects selectively
left out of packs in loose format, you would need 'repack' which
acts differently between the server-feeding-client case vs
packing-repository case.
Which is a bigger change that I did not want to show in the
quick-and-clean patch, but I would agree we would want both.
OK -- I'll put this on the back-burner with the so-called
"ent:relative" patch and I'll revisit this once your "delta"
attribute shows up in next or master.
At the moment I'm experimenting on a git repository with
a 4.5GB checkout, and 18 months of history in 4K commits
comprising 100GB (uncompressed) of blobs stored in
7 packfiles of 2GB or less. Hopefully I'll be able to say
more about tweaking packing shortly.
Thanks,
--
Dana L. How danahow@gmail.com +1 650 804 5991 cell