Re: [user] git-svn and svn cp

From: Benoit Sigoure <tsuna@lrde.epita.fr>
Date: Nov 19, 2007, 14:04 UTC
Message-ID: <A27F6A8E-705B-4D76-A84A-D25BA733EE49@lrde.epita.fr>
In-Reply-To: <vpqtzni1h17.fsf@bauges.imag.fr>

On Nov 19, 2007, at 2:49 PM, Matthieu Moy wrote:

Show 17 quoted lines

> Benoit Sigoure <tsuna@lrde.epita.fr> writes:
>
>>> 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.
>
> Well, I'm far enough from being a git-svn expert, but I suppose
> git-svn will special-case the content of tags/ and branches/
> directories, and consider copies there to be tags and branches. I
> don't know whether git-svn does it efficiently, though.
>
> If you use "svn copy" with the meaning "create a tag" with a
> destination other than tags/ directory, then, git-svn can not guess it
> was actually a tag.

No, git-svn only needs to know where to look for branches and tags so that it can replicate them on the Git side by creating remote branches. It has nothing to do with the fact that a tag or a branch happen to be a copy of something else (which isn't necessarily true, I can perfectly create a tag out of the blue which has its own unique content, same thing for branches).

The question of Gerhard was thus, why do we need to transfer "so much" data over the network when we should be able to guess that the data is already in the Git repo (because git-svn can figure out that something is a copy of something else -- because SVN records this information -- and thus save the network from downloading useless deltas). It's possible that the code can be optimized to handle this, or so I guess.

-- 
Benoit Sigoure aka Tsuna
EPITA Research and Development Laboratory