Re: [user] git-svn and svn cp

[Benoit Sigoure <tsuna@lrde.epita.fr>]

[-- Attachment #1: Type: text/plain, Size: 1460 bytes --]

On Nov 19, 2007, at 1:56 PM, Matthieu Moy wrote:

> David Kastrup <dak@gnu.org> writes:
>
>> Matthieu Moy <Matthieu.Moy@imag.fr> writes:
>>
>>>> To verify I did:
>>>> git-svn clone -s svn://www.ogersoft.at/ogerlit
>>>
>>> I guess the --tags=... and --branches=... options of git-svn can  
>>> help.
>>
>> You are aware of what the "-s" option does?

I personally don't know and I went through the code to see that it's  
an (undocumented) alias for --stdlayout.

> Not in the details. Well, I believe the accurate question (to original
> poster) is: does your svn repository use the standard svn layout
> (tags/, branches/, trunk/)?

I think this is irrelevant to the question he asked.

Now I think that the fact that SVN does "lightweight" copies by  
recording that such modification was in fact an `svn cp' / `svn mv'  
isn't important for git-svn, because the data end up in the Git  
repository which handles copies and moves much much better than SVN  
does.  But here the concerns raised by Gerhard seem to be more  
network-wise, in which case I don't know.  I looked at the code,  
things seem to happen under the hood of Git::SVN::Fetcher but I don't  
see what can be optimized (the code isn't trivial).  Most of the  
access are done through the underlying SVN Perl bindings, so if  
someone knows how to use them better, I think Eric will be eager to  
see the patches :)

-- 
Benoit Sigoure aka Tsuna
EPITA Research and Development Laboratory



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 186 bytes --]