Following up on this old thread.
I think the entire thing might be a false diagnostic on our part, and
git's default behaviour is working just fine for us.
We initially starting looking at this because the backups exploded in
size. But git is complex enough that we had a hard time examining things
retroactively. Instead, we started monitoring things going forward to
find likely causes.
What we did was to keep an eye on how new the files were in
.git/objects/pack. And we kept seeing that the large packs were brand
spanking new. Hence, the attempts at reconfiguring git, and the thread here.
But it seems we didn't look close enough. Although the timestamps
suggest that the packs are constantly being modified, the names and
contents actually stay the same.
I've been keeping a closer eye on a couple of active repositories, and
we aren't actually seeing any excessive growth in size. But the largest
pack files always have a very current modification time.
No idea what caused that initial spike in backup storage. We'll have to
revisit that if it happens again.
Regards,
--
Pierre Ossman Software Development
Cendio AB https://cendio.com
Teknikringen 8 https://twitter.com/ThinLinc
583 30 Linköping https://facebook.com/ThinLinc
Phone: +46-13-214600
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
