On Saturday 04 August 2012 23:53:58 Ramkumar Ramachandra wrote:
> Hi,
>
> Florian Achleitner wrote:
> > 1. Import linearly and split later:
> I think this approach will be a lot less messy if you can cleanly
> separate the fetching component from the mapper. Currently, svndump
> re-creates the la
Hi,
Florian Achleitner wrote:
> 1. Import linearly and split later:
I think this approach will be a lot less messy if you can cleanly
separate the fetching component from the mapper. Currently, svndump
re-creates the layout of the SVN repository. And the series you
posted last week contains a p
Hi,
On Sat, Aug 4, 2012 at 12:17 AM, Jonathan Nieder wrote:
> Hi,
>
> Florian Achleitner wrote:
>
>> Two approaches:
>> 1. Import linearly and split later:
>> One idea is to import from svn linearly, i.e. one revision on top of it's
>> predecessor, like now, and detect and split branches afterwar
Hi,
Florian Achleitner wrote:
> Two approaches:
> 1. Import linearly and split later:
> One idea is to import from svn linearly, i.e. one revision on top of it's
> predecessor, like now, and detect and split branches afterwards. The svn
> metadata is stored in git notes, so the required informa
Hi!
I'm playing around in vcs-svn/ to start a framework for detecting and
processing branches in svndumps. So I wanted to let you know about my ideas.
Two approaches:
1. Import linearly and split later:
One idea is to import from svn linearly, i.e. one revision on top of it's
predecessor, like
5 matches
Mail list logo
