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

Add permalink to svn info?

From: Dain Sundstrom <dain_at_iq80.com>
Date: 2006-06-17 03:04:21 CEST

I ran into a very strange problem today, but lucky got good help on IRC.

I was attempting to checkout revision 2473 from https://
svn.codehaus.org/openejb/trunk/openejb2. The problem was caused by
the openejb2 directory having been recut between revision 2473 and
HEAD (2684). As a naive user, I simply executed the command:

  svn co -r 2473 https://svn.codehaus.org/openejb/trunk/openejb2

Unfortunately, this doesn't work because an svn 1.3.1 client seems to
follow the lineage directory which had moved. After a long chat on
IRC, I got the correct command [2]:

  svn co https://svn.codehaus.org/openejb/trunk/openejb2@2473

My confusion was confounded because a fiend of mine still has a 1.1.4
client and the first command worked fine for him. I personally find
the first format more natural, but can understand why the second was

After thinking about the situation for a while, I think there is a
bigger problem. As a naive user, I have been creating documentation
and reports that use the first format as a permalink (e.g., to
reproduce the test results run "svn co -r 1234 http://myurl"), but
over time the first format will produce different results. I see
this as a human interface bug... like when people push on a door with
a horizontal bar no matter how big the sign is that says PULL.

Unfortunately, I think the time to change things has passed, so I'd
like to propose we make it much more clear that the proper way to
refer to a revision is with URL@REV. I think one easy to do this is
to change svn info to include a permalink entry. I'm thinking of
something like this

$svn info
Path: .
URL: https://svn.codehaus.org/openejb/trunk/openejb2
Permalink: https://svn.codehaus.org/openejb/trunk/openejb2@2473
Repository Root: https://svn.codehaus.org/openejb
Repository UUID: 2b0c1533-c60b-0410-b8bd-89f67432e5c6
Revision: 2473

What do you think?


[1] It was moved to a branch and a branch was move to trunk... long
[2] In my case I had to use svn co -r 2473 https://svn.codehaus.org/
openejb/trunk/openejb2@2473 due to a bug in 1.3.1 which has been
subsequently fixed

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jun 17 03:05:16 2006

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