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

Re: svn best practices document--possibly out of date?

From: Erik Huelsmann <ehuels_at_gmail.com>
Date: 2006-09-23 20:55:53 CEST

On 9/21/06, Beachey, Kendric <Kendric.Beachey@garmin.com> wrote:
> I'm preparing a "we are moving to svn" presentation for the team. Our
> manager has requested that I go over some best practices, so I'm shamelessly
> copying from the list found here:
> http://svn.collab.net/repos/svn/trunk/doc/user/svn-best-practices.html
> There is one section that warns about incompletely implemented commands:
> "When a file or directory is copied or renamed, the Subversion repository
> tracks that history. Unfortunately in Subversion 1.0, the only client
> subcommand which actually takes advantage of this feature is svn log. A
> number of other commands (such as svn diff and svn cat) ought to be
> automatically following rename-history, but aren't doing so yet."

> Has this been addressed in newer versions of svn? Currently we're using
> 1.3.x for our proof-of-concept stuff but some noise has been made about
> using 1.4.0 when we jump in with both feet.

Searching http://svn.collab.net/repos/svn/trunk/CHANGES tells me it's
been fixed in 1.1. Thanks for pointing this out.

The rest of your questions belong on users@, but since I'm answering
now anyway, there is a problem with the current rename support: it's
implemented as Copy+Delete, meaning that the implementation won't be
able to tell the difference between a genuine copy and a rename.



To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Sep 23 20:56:07 2006

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.