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

Re: can of worms: custom props in our tree?

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2003-11-06 05:47:43 CET

Chia-liang Kao <clkao@clkao.org> writes:

> As the name should be resolved now, I'd like to come back to the
> original topic.
> The question was if it's appropriate for me to have a 'svk:merge'
> dir_prop to '/trunk'. The reason why it's on '/trunk' rather than the
> /trunk/subversion/bindings/swig is that I am branching the whole tree
> locally. This way I could have a whole working checkout ready for
> compile, instead of having to symbolic link directories in a trunk
> checkout. And currently the merge info has to be set on the anchor of
> branching.

I don't care. I was initially one of those "eew, get that junk outta
our tree" folks. But I thought more about this today, and I realized
that if we are going to tout Subversion's modular librarized design as
a benefit for those who wish to hook in at whatever level they so
desire, why should we punish them when the choose to do so?

So, my new stance is the stance I should have taken in the first
place, and it's the same rules we have for all committers and their
commits -- don't break anything. If you're properties make your life
easier without making the rest of our lives harder, who cares if they
live in our tree. If our property design is so pathetic that actually
using custom properties presents a problem for us -- our design is

You have my blessing.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Nov 6 05:48:49 2003

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.