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

Re: Change tracking

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2005-05-06 16:26:12 CEST

On May 6, 2005, at 8:57 AM, Russ Brown wrote:

> This handles the situation where a branch being merged was worked on
> by one person, so in those cases it solves our problem. However, we do
> have some projects that are worked on by more than one developer, so
> in these cases this won't work.

Please keep in mind that 'svn blame' isn't the only way of figuring out
who did what. In subversion's own project, whenever we merge code from
one branch to another, we always say in the log message: "merging rX:Y
of foobranch to barbranch." We can then go and run 'svn log -rX:Y
foobranchURL', and examine the original changesets (and see who commit
which changeset.)

So, while I admit that having 'svn blame' would certainly be the most
*convenient* way to find the author of a line of code, it's not the
only way. The information is still available, you just have to do a
bit more digging via 'svn log' and 'svn diff'.

> Is there any indication as to when merge tracking is planned to be
> implemented? I note in the document you link to that locking is
> considered a higher priority, but the imminent release of 1.2 almost
> takes locking out of the way. Is merge tracking next, or are there
> other issues to take care of first?

See this huuuuuge thread on the dev@ list:


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri May 6 16:31:35 2005

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.