On Wed, Nov 28, 2012 at 5:57 PM, Matthew Bluhm wrote:
> 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
Guten Tag Matthew Bluhm,
am Mittwoch, 28. November 2012 um 23:57 schrieben Sie:
> The repository was started 5 1/2 years ago.
Which version does your repo has and which Subversion does your server
use? Did you just upgrade your repo or made a full dump and load cycle
with current versions of Subv
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
On Wed, Nov 28, 2012 at 3:18 PM, Thorsten Schöning
wrote:
>>
>> Does the answer change based on this?
>
> One can maybe make more clear why removing versions may have not the
> desired effect at all and is therefore just a waste of time. Your
> accidently committed and never changed images are one
On Wed, Nov 28, 2012 at 4:18 PM, Matthew Bluhm 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 cou
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 d
Guten Tag Les Mikesell,
am Mittwoch, 28. November 2012 um 22:00 schrieben Sie:
> Does the answer change based on this?
One can maybe make more clear why removing versions may have not the
desired effect at all and is therefore just a waste of time. Your
accidently committed and never changed imag
On Wed, Nov 28, 2012 at 3:42 PM, Les Mikesell wrote:
> On Wed, Nov 28, 2012 at 2:36 PM, Andy Levy 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 timestam
On Wed, Nov 28, 2012 at 2:50 PM, Thorsten Schöning
wrote:
> Guten Tag Les Mikesell,
> am Mittwoch, 28. November 2012 um 21:42 schrieben Sie:
>
>> 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
Guten Tag Les Mikesell,
am Mittwoch, 28. November 2012 um 21:42 schrieben Sie:
> 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
> some
On Wed, Nov 28, 2012 at 2:36 PM, Andy Levy 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.
>
> L
On Wed, Nov 28, 2012 at 3:10 PM, Matthew Bluhm 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 a
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.
13 matches
Mail list logo
