> From: "Philip Oakley" <philipoak...@iee.org> > Sounds like the 'git gc' needs an option to deliberately prune specific > files and/or large objects for such a case. Maybe something to discuss > on the main Git list - no doubt some discussion as to what the command > format would be and why it whould be relevenant and any regression > issues.
Well, you can get close to that by setting "--prune=now". Normally "git gc" won't remove objects to which there are no pointers until 2 weeks after the object was created. But "--prune=now" lets "git gc" eliminate them immediately if they are dangling. If the file gets recorded in a commit, but the commit is rolled back (by resetting the branch tip to an earlier commit), then the reflog for the branch may retain a pointer to the now-unused commit. You can get around that by setting gc.reflogExpire. There's more information in the "git gc" manual page. Dale -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
