--- Karl Fogel <kfogel@newton.ch.collab.net> wrote:
> "Morten Ludvigsen" <morten@2ps.dk> writes:
> > http://svn.collab.net/repos/svn/!svn/bc/2000/
> >
> > This looks to me like revision 2000 :-) Is this
> correct and is it likely to
> > change?
>
> Yes and yes, heh.
>
> It is correct, but the format of these URLs can be
> changed at any time
> by the server, and this may actually happen. In
> other words, do it by
> hand for as long as it works, if you want, but don't
> write software
> that depends on it please :-).
I'm actually toying with the idea of the repo looking
like the following (assuming the repo is in
/.svn-repo):
1. A project p0 will reside in /.svn-repo/p0
2. Project p0 will have a main branch as
/.svn-repo/p0/main
3. The real stuff exists in /.svn-repo/p0/main/LATEST
4. Each checkin onto main will create a sequential
revision number tag (eg /.svn-repo/p0/main/0,
/.svn-repo/p0/main/1, ...)
5. A symbolic label may be created to point to any of
main's revisions
6. A branch b0 may be created from a revision off of
main (eg /.svn-repo/p0/main/b0 branches off of
/.svn-repo/p0/main/2)
7. Branch b0 will act just like the main branch with
regards to LATEST, revision numbers, and other
branches
Those familiar with ClearCase will recognize the
structure.
Those using Apache will be able to look at any
revision without the use of magic URLs.
An assumption I've been making (which I hope someone
will confirm) is that it's possible to create a
post-checkin trigger that'll create the branch
revision numbers.
Comments?
Thanks,
Noel
__________________________________________________
Do you Yahoo!?
Faith Hill - Exclusive Performances, Videos & More
http://faith.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Oct 9 15:30:10 2002