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

RE: Code Loss!?

From: Irvine, Chuck R [EQ] <Chuck.R.Irvine_at_Embarq.com>
Date: 2007-04-16 23:31:58 CEST

> On 4/16/07, Irvine, Chuck R [EQ] <Chuck.R.Irvine@embarq.com> wrote:
> > > Is this something that might be covered/coverable in the merge
> > > tracking functionality?
> >
> > As far as been indicated on the mailing list, no this won't be
> > addressed in the merge tracking initiaitve. The most current
> > information is that fixing this problem will be considered for
> > inclusion in 1.6.
> Thanks - can I ask one further question (we've only been
> using Subversion for a few months, having come across from
> CVS). My understanding is that Subversion has no distinction
> between a file that has been copied, and a file that has been
> renamed. In both cases the new file is simply a file that
> has inherited history. Is this correct?

I think you are correct. A rename in Subversion is implemented as a copy
and a delete. The Subversion designers have recognized for some time
that this was a design mistake.

> The reason I ask is that I think there is a difference. The
> main one being the difference between creating a branch, and
> renaming a file on that branch. I assume the lack of
> distinction between these two activities is the reason why
> this functionality is missing. Correct?

Sorry, I didn't really understand this paragraph.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Apr 16 23:32:33 2007

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