Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> wrote: > > Oh, and to make sure I'm not lying I actually did test this, but I also > noticed that "git clone" no longer marks the initial pack-file with > "keep", so it looks like "git gc" will then break the link. That's sad. I > wonder when that changed, or maybe I'm just confused and it never did. It was a bug in git-clone that we were recording the .keep file on initial clone. We left the lock file in place after the fetch pack call was done, but didn't remove it after the refs were updated. If we want to go back to .keep'ing the original pack creating during clone it probably should be threshold based. For many smaller projects with only a 25M pack (or less) there is no point in .keep'ing that first pack. For larger projects where the pack is over a few hundred megabytes, then yea, maybe there is value in .keep'ing it during clone. -- Shawn. -- 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
