vinay modi wrote:
>My organization's svn repository size has grown too large and most of the
>old revisions of documents are never being used.
>[...]
>Now, I want to keep only the last 2 revisions of all documents i.e 2 for A,
>2 for B, 2 for C and 1 for D..
http://subversion.apache.org/fa
Hello,
You can create a new repository then get the second to last revision and
use that to create a new project in that new repository. Then create a
working copy and replace it with the current revision. Then do a commit
and you're done.
JPM
From: v
Hi
My organization's svn repository size has grown too large and most of the
old revisions of documents are never being used.
Consider I have 4 documents in my repository, of which I have 10 revisions:
4 for document A
3 for document B
2 for document C
1 for document D.
Now, I want to keep only
Hi Stefan,
Well it's early on in the process, the script works, but I've not tested it
on a local repository yet with
a suitably sized project. The remote Tomcat Apache project (approx 64MB)
that I did "checked out"
slightly slower with the script. I haven't delved into i/o stats or
network late
On Tue, Sep 04, 2012 at 03:26:36PM +0100, Jonathan Holloway wrote:
> then forking a process/starting a thread to svn update the subfolders?
> Does this make sense from a
> performance point of view or is the bottleneck of disk I/O always
> hit pretty early on by doing this?
Did you make any perfo
On Tue, Sep 4, 2012 at 10:26 AM, Jonathan Holloway <
jonathan.hollo...@gmail.com> wrote:
>
> Has anybody had any success in parallelising Subversion checkouts in the
> past on a subfolder level
> to improve performance at all?
>
> By this I mean using svn sparse directories with --depth intermedia
Holger Schmidt writes:
> What can I do to get rid of the error?
Upgrade to 1.7.
$ svn1.6 st wc1
svn: 'wc/dir1/dir2/file1' is not under version control
$ svn1.7 st wc2
Status against revision: 2
--
Philip
Hello,
I have a directory dir1/dir2 in my SVN working copy that has depth=empty
set, e.g. after "svn up --set-depth empty". Someone else deletes a file
in that ignored directory. Now I do a "svn st -u" in my working copy
and get an error:
svn: 'dir1/dir2/file1' is not under version control