Split the dumpfile to smaller dumpfiles or try a newer version of svnadmin.
(or dive into the source and help us plug that memory leak --- compile
with APR pool debugging enabled)
Victor Sudakov wrote on Fri, Dec 31, 2010 at 09:07:32 +0600:
> Colleagues,
>
> I have a CVS repository sized 54M wi
Daniel Shahaf wrote:
> Split the dumpfile to smaller dumpfiles
How do I do that? I have not found such an option in cvs2svn.
I don't mind writing a script if I knew the idea how to split the dump.
I haven't found any "svnadmin load" option to import part of a dump
either. man what?
> or try a n
I migrated a large CVS repository (25-50 GB) to SVN years ago on SVN
1.3. Our repo had many sections (projects) within it. We had to
migrate each project independently so that it's team could coordinate
when they migrated to SVN. As such, I dumped each project when ready
and then svnadmin lo
On Thu, 2010-12-30 at 23:03 +0200, Daniel Shahaf wrote:
> > > I also tried:
> > >
> > > svn rm a.txt
> > > ln -s b.txt a.txt
>
> At this point you need to:
>
> svn add a.txt
Thanks, I'll try it the next time I encounter this situation.
Brian Brophy wrote:
> I migrated a large CVS repository (25-50 GB) to SVN years ago on SVN
> 1.3. Our repo had many sections (projects) within it. We had to
> migrate each project independently so that it's team could coordinate
> when they migrated to SVN. As such, I dumped each project when
Google is your friend: svndumptool
You moght need to append a .py
Also if this is a _top post_ it's three phone what done it... Haven't
figured out how to control where it puts the reply
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonse
> On 31 Dec 2010 15:10, "Victor Sudakov" wrote:
> > Daniel Shahaf wrote:
> >> (or dive into the source and help us plug that memory leak --- compile
> >> with APR pool debugging enabled)
> >
> > I will try to do that but unfortunately I need some immediate
> > workaround :(
> >
Thanks. I was ref
