[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: copy newly added file

From: Fejes József <fejes_at_joco.name>
Date: Mon, 03 Aug 2009 14:55:15 +0200

>>>> I know that a newly added file doesn't have a history yet but why
>>>> does
>>>> that matter? That + sign could appear just like it does with another
>>>> file that does have a history, it should be a link nonetheless. I
>>>> don't
>>> Well the + means "copied with history", but clearly from svn's
>>> perspective there is no history, so I think the output is correct. I
>>> don't know whether the developers think that the overall behavior is
>>> correct.
>> The lack of + made me think that these files are not cheap copies,
>> just
>> regular, space-wasting copies, but clearly I was wrong about the
>> meaning
>> of it. So is it cheap or not? How do I tell the difference without
>> the +
>> sign?
> I don't know if this copy will be cheap. But you can create a
> throwaway repository and try it out.
> If you find the copy is not cheap, and you don't want to use file-
> level externals for this, then I recommend you do the other thing you
> don't want to do, and commit the lib directory first, then create the
> web* directories and copy things to them and commit them second. You
> say it's a pain, but if this is a type of build you do often, I
> expect you already have a script for it, so just change these steps
> in the script.

Ok, I experimented a little with a local repository, using the latest
version of TortoiseSVN. I found that the copy of a newly added file is not
cheap. Should I report this as a bug then?

And thanks for pointing out file level externals. The idea sounds better
than copying, I'll stick to that. But let's not close the above issue yet
about cheap copies.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-08-03 14:57:36 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.