There were some binary files that were included as part of the projects that weren't necessary, so its tons of seemingly small mistakes.
The repository was started 5 1/2 years ago. Revision #6,000 was about 2 years ago. I have never used any history older than 24 months. Even though 10 GB doesn't seem big, about 2/3 of it is a waste, so its wasting time and money. I agree that the whole idea is too keep the history, but oldest transactions provide the least value for me. mb On Wed, Nov 28, 2012 at 4:28 PM, Andy Levy <andy.l...@gmail.com> wrote: > > > On Wed, Nov 28, 2012 at 4:18 PM, Matthew Bluhm <matthew.bl...@bluhm.biz>wrote: > >> My repository is now over 10GB and it is rather cumbersome to take care >> of. >> >> There has been many mistakes such as committing extra files. >> >> The older revisions provide no value and only cause headaches. >> >> I initially thought that I could export out the repository at revision >> 6,000 then just apply a dump of transactions 6,001 to HEAD >> >> > > > Do you truly have 6000 revisions - two thirds of your whole repository - > which have NO value whatsoever? Probably not. Those revisions are the > history of what you're producing. In the grand scheme of things, a 10GB > repository isn't really that large. > > Rather than throw away *all* of your history, have you considered the > possibility of removing just those revisions where large files (ISO images) > which never should have been committed? This will preserve your history and > reduce your repository size, and skip throwing the baby out with the > bathwater. > > > On Wed, Nov 28, 2012 at 3:42 PM, Les Mikesell <lesmikes...@gmail.com>wrote: >> >>> On Wed, Nov 28, 2012 at 2:36 PM, Andy Levy <andy.l...@gmail.com> wrote: >>> > >>> >> Is there an easy way to purge out the earliest 6,000 Revisions of the >>> >> 9,600 that are in my repository? >>> >> >>> >> In a perfect world I would keep my revision numbers and timestamps, >>> but >>> >> that isn't 100% required. >>> >> >>> > >>> > Short answer: No. >>> > >>> > Longer answer: It can be done, but everyone will have to check out new >>> > working copies and you might get weird results due to the loss of >>> history. >>> > There is no "easy" way to do it, but if all you're doing is cutting >>> off the >>> > first X revisions it's not the most complex task. You will keep the >>> commit >>> > timestamps, but the revision numbers will be reset (unless you enter >>> dummy >>> > revisions, which will then make your repository appear to own a >>> modified >>> > DeLorean, unless you then further mangle those dummy revisions to >>> change >>> > their timestamps). >>> > >>> > Version control systems are designed to keep your history. "Purging" >>> goes >>> > against this core concept. Why are you embarking on this endeavor? >>> >>> It's pretty much just a matter of time until someone does something >>> that shouldn't have been done in any repository. Even if the answer >>> is always going to be 'it can't be done', why question the motives of >>> someone trying to fix things? >>> >>> -- >>> Les Mikesell >>> lesmikes...@gmail.com >>> >> >> >
