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

RE: Global Revision keyword, again and again

From: Erik Anderson <erikba_at_teamworkgroup.com>
Date: 2005-07-30 01:13:20 CEST

Umm, no. If someone checked in an updated foo.c at rev 25 and you have
not updated since then, then an svn co -r 30 would receive foo.c at rev 25
and bar.c at revision 30, while your WC would still show foo.c at rev 20

-----Original Message-----
From: Jan W. Hentsch [mailto:jwh@csmed.de]
Sent: Friday, July 29, 2005 3:59 PM
To: 'Hari Kodungallur'
Cc: users@subversion.tigris.org
Subject: RE: Global Revision keyword, again and again

> In this situation, the "program --version" would not give the
> right information. The user might have foo.c at revision 20
> and bar.c at revision 30. It is a mistake to say that the
> user's code is at revision 20. It is also a mistake to say
> that it is at revision 30. There can not be one revision
> representing the whole working copy.

You are right, the program --version would give me the highest
revision which belongs to one of its components.

When I take this information an do a svn co -r 30 I would still get
foo.c at rev 20 and bar.c at rev 30. Even if foo.c got an increased
revision number later on, I would get it the same way it got
assigned to my project when my wished keyword was automatically updated,

cu jwh

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

  • application/x-pkcs7-signature attachment: smime.p7s
Received on Sat Jul 30 01:15:38 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.