On Fri, Apr 9, 2010 at 9:37 PM, Greg Stein <gstein_at_gmail.com> wrote:
> On Sat, Apr 10, 2010 at 00:18, 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/*/*'.
> I think people are asking about formalizing the trunks/tags/branches
> ("TTB") concepts (or some appropriate variant), and adding some
> built-in technical enforcement of the concepts. Then some further
> layering of merge handling within that restricted environment.
> These kinds of changes would be quite welcome, I believe. "If you want
> solid merge-tracking, both performant and easy, then do XYZ. There are
> more open/flexible approaches, but those approaches come with issues."
Thanks Greg, exactly what I mean.
I *do* like flexibility: life is crazy and you never know what
configuration you'll need in your next project. So it would be good to
preserver the current svn ability to work with any folder as with TTB.
BUT: I want svn to reflect the way 99% of programmers work 99% of their time.
If explicit branching can help to simplify merging algorithms, great.
Tagging can prevent newbies (or absent minded pros) from modifying
released code - great!
Received on 2010-04-10 22:58:00 CEST