>--- Forwarded mail from [EMAIL PROTECTED] >Mark writes: >> >> If one wants to tag the latest on a branch, why should one have to create a >> workarea to do it?
>How do you know you want to tag the latest on a branch? Either you have >no idea what the "latest" actually is, or you know that no one is going >to be trying to commit changes while you're tagging the files. In >neither case is directory-at-a-time locking going to make any difference. Most of the time it's the former. But you do know what was "latest at a given time". And "a given time" could possibly be "now". Given this, everything becomes pretty well-defined and rtag can run with or without two-phase locking. There is one exception: The branch tag moves during the rtag. I can envision someone using a floating branch tag to identify the approved branch for the next release, but I have not yet heard of anyone actually doing that. So using a branch tag/timestamp pair is very likely to be safe. But if you want to avoid the floating branch tag situation then two-phase locking is still required. >--- End of forwarded message from [EMAIL PROTECTED] _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
