On 5/22/2013 7:56 PM, Branko Čibej wrote:
On 23.05.2013 04:33, David Chapman wrote:
On 5/22/2013 4:57 PM, Varnau, Steve (Seaquest R&D) wrote:
So, am not saying there is anything fundamentally wrong with how
“tags” work now. They just don’t fit our desired semantics, so we
don’t use them. I am also not saying how a better tag or label
feature should be implemented, but for our usage, a symbolic name or
symbolic link for a path@revision would be a very useful thing.
I'd say tags don't fit your repository configuration. See if you can
get a pre-commit hook that blocks modifications to the tags directory
tree within the repository.
I'm confused ... why would you need a special pre-commit hook for
something like that? I would expect access control to be good enough.
Just make the tags tree in the repository read-only for most users.
(N.B., having actually immutable tags would be a nice feature, but
they're not required to solve your problem.)
Access controls implies more than what the original poster was asking.
Right now anyone can make a "tag" in his development environment simply
by recalling the revision number. Access controls could work and are a
reasonable suggestion in many cases. I tend not to think of them because
I usually work in more-open environments where anyone can commit.
--
David Chapman dcchap...@acm.org
Chapman Consulting -- San Jose, CA
Software Development Done Right.
www.chapman-consulting-sj.com
