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

RE: Revision numbers in subversion...

From: Bob Aiello <bob.aiello_at_FXALL.com>
Date: 2007-09-09 19:18:30 CEST

ahh.. that makes sense - Thank you.
I just found that a user deleted a branch and was making
changes directly on the tag itself. Do you have suggestions
for how to prevent this?

        -----Original Message-----
        From: Matt Sickler [mailto:crazyfordynamite@gmail.com]
        Sent: Sun 9/9/2007 1:05 PM
        To: Bob Aiello
        Cc: users@subversion.tigris.org
        Subject: Re: Revision numbers in subversion...

        The revision number is repository wide. Your three commands tell svn
        to check out those three locations as they existed at the time when
        the repository was at revision 2222.
        On 9/8/07, Bob Aiello <bob.aiello@fxall.com> wrote:
> It appears that the revision number is subversion is
> specific to the trunk/tag/branch that code is committed
> to. By convention variants in the code are supposed
> to be made on the trunk or on development branches
> when needed (e.g. bug fix). I had originally thought
> that the SVN revision number was a changeset on
> a repository wide basis (which I am is what I read
> in one of the svn books that I have). But I have found
> that the revision number is actually specific to the
> branch/tag/trunk where the changes were committed.
> so if I
> export -r 2222 svn+ssh://mysvnserver/opt/svn/myproject/trunk
> it is different than
> export -r 2222 svn+ssh://mysvnserver/opt/svn/myproject/branch/mydevbranch
> and different than
> export -r 2222 svn+ssh://mysvnserver/opt/svn/myproject/tag/1.0.0
> (unless of course I committed the same changes to all three locations
> myself
> Is there a repository wide revision number?
> Bob
Received on Sun Sep 9 19:15:22 2007

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.