aloha!
Yesterday I run the following command on the updated GIT respository:
git repack -adf --window=250000 --depth=100000
After 280 minutes or so it finished, but the strange thing was that
the resulting pack-file was larger than before. I had expected that
it should be smaler, or at least the same size as before.
kjetil git (my_next)$ ls -l .git/objects/pack/*
-r-------- 1 kjetil kjetil 2757280 2009-03-16 15:18 .git/objects/pack/pack-c5f15d5c48d6b3902a49046d7e8a8d717e167051.idx
-r-------- 1 kjetil kjetil 19961120 2009-03-16 15:18 .git/objects/pack/pack-c5f15d5c48d6b3902a49046d7e8a8d717e167051.pack
Before I started the pack file was around 19 250 000 bytes, and was
the result of the following commands:
1) git repack -adf --window=250000 --depth=20000
- not completly sure about the --window number here
- the resulting pack file was a litle less than 19 100 000
2) 'git fetch' to get the latest GIT patches
3) since 'git fetch' always make an extra new "smal" pack file, I run
the command 'git repack -ad --window=40000 --depth=10000' to be
able to get one singel pack file of 19 250 000 bytes or so.
I can think of one thing which is spesial with the "--depth=100000"
number, and that is that it is now larger than the total number of
objects in the pack, which is around 96000 to 97000, or so.
I have run 'git fsck --strict --full' on the pack with no resulting
error/debug output or change in the file size.
Any help on how to debug this?
-- kjetil
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
