svn copy and history - quick question

[Z W <mp...@gmail.com>]

Hi All

We are SVN newbies here.
We plan to do an svn copy (of a branch to another trunk).
Does "svn copy" command copies all the history of the file and folder
revisoins too ?

Thanks

RE: svn copy and history - quick question

[Bob Archer <Bo...@amsi.com>]

> Hi All
> 
> We are SVN newbies here.
> We plan to do an svn copy (of a branch to another trunk).
> Does "svn copy" command copies all the history of the file and folder revisoins
> too ?
> 
> Thanks

The simple answer is... yes. 

BOb

Re: svn copy and history - quick question

[C M <cm...@gmail.com>]

As a SVN newbie myself, I suggest you set up a SVN sandbox and try out the
basic functionality within it.

You will get a better understanding of how SVN works by trying out various
commands.

Regards.
Amad

On Thu, Feb 14, 2013 at 1:58 PM, Z W <mp...@gmail.com> wrote:

> Hi All
>
> We are SVN newbies here.
> We plan to do an svn copy (of a branch to another trunk).
> Does "svn copy" command copies all the history of the file and folder
> revisoins too ?
>
> Thanks
>

Re: svn copy and history - quick question

["C. Michael Pilato" <cm...@collab.net>]

On 02/14/2013 02:58 PM, Z W wrote:
> Hi All
> 
> We are SVN newbies here.
> We plan to do an svn copy (of a branch to another trunk).
> Does "svn copy" command copies all the history of the file and folder
> revisoins too ?

I'm going to hesitantly say "yes" here.  Yes, if you copy a directory the
result will contain all the same stuff that the original had.  Yes, it will
have essentially the same history as the original.

But perhaps it's best not to think about 'svn copy' "copying history" --
depending on how you interpret those works, that might imply a situation in
which all the changes associated with the copied item are being duplicated,
as if they've been made all over again.  Rather, what happens is that 'svn
copy' creates a single new version of an existing versioned file or
directory as a continuation of the history of the original object, just at a
different location and without discontinuing the life of the object at its
original location.

It may help to visualize it as a fork in the road of the copied object's
historical path.  Naturally, such a fork will look exactly like the original
at first -- same content (for files), same children (for directories), same
revision log of changes, etc.  After all, every change made thus far in the
history of that object is common to both sides of that fork.  But from that
point on, the copied object is free to diverge historically from the original.


-- 
C. Michael Pilato <cm...@collab.net>
CollabNet   <>   www.collab.net   <>   Enterprise Cloud Development