Cutting history

[Enrico Weigelt <weigelt@metux.de>]

Hi folks,


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).


What do you think about this ?


cu
-- 
----------------------------------------------------------------------
 Enrico Weigelt, metux IT service -- http://www.metux.de/

 phone:  +49 36207 519931  email: weigelt@metux.de
 mobile: +49 151 27565287  icq:   210169427         skype: nekrad666
----------------------------------------------------------------------
 Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme
----------------------------------------------------------------------