-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sep 29, 2005, at 11:05, David Jackman wrote:
I was of the presumption that (at least with CVS) when you do a tag it
tags the version of each file that are present on your machine,
regardless of what the latest version is on the SCM server. I don't
know for sure if the SCM plugin command is doing it this way (since it
is possible to have it tag the latest version without regard for
what's present locally), but I can't imagine why it wouldn't.
-----Original Message-----
From: Michael Böckling [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 29, 2005 9:46 AM
To: [email protected]
Subject: SCM Tagging / Releasing
I'd like to know whether tagging with SCM is problematic with
concurrent access. Say, I want to make a release, and while SCM is
running and does its job, some developer commits a patch to the
repository. What happens?
Do I get an inconsistent state, or is that impossible (be it with CVS
or SVN)?
This information is quite important for me, and I thank everyone in
advance who knows something.
With SVN, at least, commits are atomic, so it's not possible [1] for
the repository to end up in an inconsistent state. The worst that
should happen is that the commit fails and you have to try again.
This is one of the reasons I've switched from CVS to SVN.
[1] Never say never. However, if your SVN repository ends up in an
inconsistent state, you have problems bigger than someone else
committing while you're tagging a release.
- --
Craig S. Cottingham
[EMAIL PROTECTED]
OpenPGP key available from:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x7977F79C
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)
iD8DBQFDPBhCEJLQ3Hl395wRAvDBAKDTl4ASMLGEaO82Vvojy/ssuS5mrACdFGHy
H/1Y8S6CgQyO/6GG9hs1RJY=
=DOtR
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
