Russ kirjoitti:
> You can also keep the original revision #s with svndumpfilter, so no regexing
> necessary.
Yeah, svnadmin + svndumpfilter was pretty straightforward with this
approach and took this route since it's "easier". :)
Now I only need to ripoff tickets from old Trac to new Trac and
ac] Re: Splitting up a project
Lots of scripts to regex the ticket tables. svndumpfilter shows you
the mapping from old rev # to new as it processes, so you capture
that output and rewrite the ticket bodies based on that,
--Noah
On Oct 10, 2006, at 12:55 PM, Jani Tiainen wrote:
>
> Noa
Lots of scripts to regex the ticket tables. svndumpfilter shows you
the mapping from old rev # to new as it processes, so you capture
that output and rewrite the ticket bodies based on that,
--Noah
On Oct 10, 2006, at 12:55 PM, Jani Tiainen wrote:
>
> Noah Kantrowitz kirjoitti:
>> Having do
Noah Kantrowitz kirjoitti:
> Having done this before on a large site, its painful. svndumpfilter
> is somewhat helpful in splitting the repos, though you need to post-
> process the results a bit to strip the leading path component. For
> the Trac itself I used the DatamoverPlugin and WikiRen
Russ kirjoitti:
> I ran into this the other day.. Either split up your repo if your projects
> are not related to one another or use the full path to svn in trac.. Such as
> /path/to/repo/proj1 and in the second trac environment, /path/to/repo/proj2.
> Instead of just /path/to/repo.
(top pos
I ran into this the other day.. Either split up your repo if your projects are
not related to one another or use the full path to svn in trac.. Such as
/path/to/repo/proj1 and in the second trac environment, /path/to/repo/proj2.
Instead of just /path/to/repo.
Russ
Sent wirelessly via BlackBer
Having done this before on a large site, its painful. svndumpfilter
is somewhat helpful in splitting the repos, though you need to post-
process the results a bit to strip the leading path component. For
the Trac itself I used the DatamoverPlugin and WikiRename to split up
the wiki pages an
