Jesper Bork <Jesper.Bork@eu.fkilogistex.com> writes:
> directories. You could say that this reflects a lack of self-dicipline, but
> I believe that unless an even easier way of doing stuff like that exists,
> this is what people do.
You could say that... if you were the type to confuse a carefully
thought-out design decision with a character flaw on the part of the
developers. But you're not that type, I hope.
:-(
Seriously, dude: You can give your technical opinion here without
resorting to ad hominem cheap shots :-). I assure you the decision to
store .svn/ directories the same way CVS stores CVS/ directories was
not made from mindless habit, but from consideration of all the
options. We are aware that there are both advantages and
disadvantages; you, apparently, are only aware of the disadvantages.
> As far as I have been able to read, there is no way to configure Subversion
> to do otherwise, e.g. place this information in some kind of designated
> meta-data directory of a project. We have actually discussed building a
> modified CVS with those catalogs relocated to a (configurable) location not
> intruding into the source branch, and will have to do the same in order to
> consider Subversion an alternative. I frankly do think that an SCM tool
> should not be intrusive with regard to the source code modules. Would it be
> possible for you or us to add such an option to you otherwise very promising
> product ?
That is correct, there is currently no way to configure Subversion to
do otherwise. There may be such an option after 1.0, but we can't
promise.
Good luck! I hope you find Subversion useful anyway.
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Aug 25 17:27:29 2003