----- Original Message ----- From: Enrico Weigelt Date: 7/9/2010 9:25 PM
I'm using git for automatic backups (eg. database dumps). This works quite well, but as time goes, the history (and so the repo) gets larger and larger. It would be really nice to allow cutting off old stuff (eg. after N commits in the past). Maybe that could be done by introducing "stopper" tags: commits that have an stopper-tag may have missing parents, and git-gc can be told to ignore those parents and throw away everything behind the stopper (if not referenced otherwise). A probably cleaner, but more invasive way could be making refs to vectors, which may contain stop points (multiple ones in case of merges) additionally to the start point. Remote transmits only contain the commits within this range, and GC also just scans the range (instead of following all parents).
Your post reminded me of this: http://progit.org/2010/03/17/replace.html Josh -- 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