[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Subversion Vision and Roadmap Proposal

From: Vadim Chekan <kot.begemot_at_gmail.com>
Date: Sat, 10 Apr 2010 13:46:28 -0700

Yes, I do use commit hooks and permissions. But it is fixing a
problem. And why should we fix a problem if it could be avoided?
The notion of a "snapshot" is clearly understood by everybody, so why
not to introduce it as a first class feature?

On Fri, Apr 9, 2010 at 9:18 PM, Alexey Neyman <stilor_at_att.net> wrote:
> Have you looked at pre-commit hooks that may serve that purpose? I think
> svnperms.py may be what you're looking for - just disallow all operations
> except additions on 'tags/*', and disallow all operations on 'tags/*/*'.
> Hope that helps,
> Alexey.
> On Friday 09 April 2010 05:56:44 pm Vadim Chekan wrote:
>> On Fri, Apr 9, 2010 at 11:31 AM, B Smith-Mannschott
>> <bsmith.occs_at_gmail.com> wrote:
>> > On Fri, Apr 9, 2010 at 10:13, Vadim Chekan <kot.begemot_at_gmail.com> wrote:
>> >> P.S. Pleeeease, introduce true tags, no more "lets pretend this copy is
>> >> a tag".
>> >
>> > What's a "true" tag? What's it good for? How would it behave?
>> Tag is named snapshot. When I do release, I want to tag the code I've
>> just released so that nobody can modify it.
>> I want to be sure that in any moment in the future, I can checkout
>> "tags/product-1.0" and I will get exactly what has been released and I
>> want a guarantee that no genius "fixed" something in tags/
>> Vadim.

From RFC 2631: In ASN.1, EXPLICIT tagging is implicit unless IMPLICIT
is explicitly specified
Received on 2010-04-10 22:46:57 CEST

This is an archived mail posted to the Subversion Dev mailing list.