Re: ClearCase-like repo structure (Was: Accessing different revs via Apache?)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I don't know the answers to your other questions, but:

On Wednesday 09 October 2002 11:13, you wrote:
> 3. Will the post-commit trigger execute all commands
> that I may care about (eg mkdir, import)?

I think the only thing you'd want to do is copy and possibly mkdir. The
post-commit doesn't have a working copy, so there would be no import.

> Also, I still need to think about an efficient way to
> figure out the next per-branch revision number. Maybe
> I can make it or the current LATEST revision an
> attribute (oops, I mean property ;-) of the branch?

This is related to possible locking issues. If you don't have a lock
surrounding when you check the property and when you create the directory,
then that will definitely cause problems. Maybe Subversion has that problem
solved already?

> Yup, this is what I had in mind, but, what happened to
> r2?

I was just trying to demonstrate that there isn't really a connection between
the labels and actual revisions. The post-commit script will create a new
revision for each copy in addition to the original commit, so in real life
the revision numbers of the labels would increase by two every time, in
addition to increases do to branch commits.

- --
Peter Davis
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9pHtFhDAgUT1yirARAnEZAJ4vKeVsKiLfUdjwmS1TGIWGwGFRegCgmsqG
SEAULztTCNs2oxkA+cUF0Do=
=BnyX
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Oct 9 20:56:31 2002