storing binary blobs, or otherwise synching them
eddy.petrisor at gmail.com
Thu Aug 31 20:50:00 CEST 2006
On 31/08/06, Eddy Petrişor <eddy.petrisor at gmail.com> wrote:
> On 31/08/06, Ken Bloom <kbloom at gmail.com> wrote:
> > > Ideally if subversion ever allows it, a truncated
> > > feature would be nice for something like my volatile
> > > repository. If I could just say truncate history up
> > > to 3 months ago, that would be cool!
> > You can accomplish this with
> > $ svnadmin dump -r LOWER
> > then create a new repository
> > $ svnadmin load
> > (svnadmin dump will give you a complete first revision unless you use
> > the --incremental switch)
> > Although an svnadmin truncate option would be quite cool, because I
> > think this will cause all of the revision numbers to change and
> > working directories will probably break as a result.
> Add to you advice the option to keep empty revisions for the ones
> filtered out and you don't have that problem.
Hmm, now I realise you were talking about the vapourware code which
should truncate; implementing a similar mechanism for truncate
(keeping empty old revion numbers) would also workaround the problem
(if that problem is there by SVN's design).
"Imagination is more important than knowledge" A.Einstein
More information about the vcs-home