Re: FR: forbit to commit into a tag
Please don't, perhaps I need to change an externals definition in my tags folder to point to some other svn repo tag, I need to have commit access to that folder in that case. Kind regards, Marijn On Feb 17, 2009, at 9:21 AM, mguske wrote: Hi, please forbid to commit into a ./tags-path if the repository layout is the basic with trunk/branches/tags. I know, those directories are only a convention, but before it accidentally happen. Thanks, ~ Markus --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Versions group. To post to this group, send email to versions@googlegroups.com To unsubscribe from this group, send email to versions+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/versions?hl=en -~--~~~~--~~--~--~---
Re: FR: forbit to commit into a tag
Hi, On 17 Feb., 17:18, Quinn Taylor quinntay...@mac.com wrote: Agreed, this is something that should be done in the repository itself (as a pre-commit hook) sometimes you're not able to place a hook into the repository - e.g. in large scaled projects, when you work as a consultant. And: customers will not always listen ;-), but that's o.k. or by educating users. The same, you can only try to teach, every day and your colleagues learn each day, more and more. But version control can still be a little bit, let me say: difficult. Even if it were implemented in Versions (which is a bad idea) the user could just switch to Terminal or another client and commit to /tags, Right, but most of the time, the users won't use the shell - that could sometimes be your luck. Let me say, they are afraid of it, like a developer branch and so on. so *every* client would have to forbid this. Save yourself the headache, take the time to learn about pre-commit hooks and disallow any overwriting of a tag. I agree, but sometimes you doesn't have the admin priviledges granted and this feature could also save your day. I requested this feature based on own experiences. Finally, you're right, best solution is to prevent this via hook- scripts. But this convention supporting feature would also be great. ~ Markus - Quinn On Feb 17, 2009, at 3:11 AM, Marijn Huizendveld wrote: Please don't, perhaps I need to change an externals definition in my tags folder to point to some other svn repo tag, I need to have commit access to that folder in that case. Kind regards, Marijn On Feb 17, 2009, at 9:21 AM, mguske wrote: Hi, please forbid to commit into a ./tags-path if the repository layout is the basic with trunk/branches/tags. I know, those directories are only a convention, but before it accidentally happen. Thanks, ~ Markus smime.p7s 3KAnzeigenHerunterladen --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Versions group. To post to this group, send email to versions@googlegroups.com To unsubscribe from this group, send email to versions+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/versions?hl=en -~--~~~~--~~--~--~---
Re: FR: forbit to commit into a tag
I understand your quandry, but I can't agree with that approach unless it's strictly optional, off by default, and fairly configurable. It would be nice if SVN could make it easier to forbid committing to tags (perhaps except for a certain group of admin users) on the repository side, maybe even as a default. However, this is a difficult problem—either on client or server—since repository structure varies greatly, and guessing whether or not commits should be allowed is unreliable. For example, some repositories contain multiple projects, and the root level does not always contain trunk/branches/tags as you'd expect. Even if you look down X levels, there is the problem of forbidding access to a directory named tags which has nothing to do with tagged revisions. In practice, this problem is just not that easy to solve... As far as user education, I'm generally not one to use this as a cop- out for honest requests, but it generally works quite well. In your case, if the users are afraid of the Terminal, perhaps you could impress upon them an equal fear of committing to a tag after it has been written. Tell them it will screw up your process. Tell them the repository admin will come banging on their door. Tell them it can affect their bonuses, whatever. ;-) When you give people a strict rule and explain why, it generally works. If they don't understand why, and Versions won't let them commit to tags, they'll end up being confused and frustrated, and potentially more likely to explore other options (not just Terminal, but other GUIs) due to a perception that Versions must be broken. Sorry to be a naysayer, but I think that user education and persistence with the repo admins are the best courses of action. - Quinn On Feb 17, 2009, at 8:51 AM, mguske wrote: I agree, but sometimes you doesn't have the admin priviledges granted and this feature could also save your day. I requested this feature based on own experiences. Finally, you're right, best solution is to prevent this via hook- scripts. But this convention supporting feature would also be great. ~ Markus On Feb 17, 2009, at 3:11 AM, Marijn Huizendveld wrote: Please don't, perhaps I need to change an externals definition in my tags folder to point to some other svn repo tag, I need to have commit access to that folder in that case. Kind regards, Marijn On Feb 17, 2009, at 9:21 AM, mguske wrote: Hi, please forbid to commit into a ./tags-path if the repository layout is the basic with trunk/branches/tags. I know, those directories are only a convention, but before it accidentally happen. Thanks, ~ Markus smime.p7s Description: S/MIME cryptographic signature
