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

Re: The "follow copy history" initiative

From: John Peacock <jpeacock_at_rowman.com>
Date: 2004-04-06 17:53:47 CEST

Folker Schamel wrote:

> To avoid misunderstandings:
> I'm only taling about renames / copies *within* a project, e.g.
> *within* trunk. I'm not talking about branch / tag copies.

As Ben already pointed out, there are no distinctions between copies, no matter
where they are. Copies are copies are copies. What you /mean/ by a particular
copy within your repository is unknowable by Subversion (or any tool for that
matter). You are responsible for developing your own work methods which may
lend significance to "copy within trunk" vs "copy to branch" but the tool cannot
do that for you.

> My point is: The need for a merge is independent
> from the file still having the same name,
> being renamed or being copied within a project.

This feature you are asking about (splitting sourcefiles and automatic merging
of bugfixes) is not within the scope of Subversion. You as the developer must
merge code changes like that; unless a SCM tool had a copy-history at the line
level, there is little or nothing that _any_ tool could do for you. AFAICT,
your request has nothing to do with the larger issue of "follow copy history" as
it exists in Subversion.


John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Suite H
Lanham, MD  20706
301-459-3366 x.5010
fax 301-429-5748
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Apr 6 17:53:50 2004

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

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