Greg Stein <gstein@lyra.org> writes:
> It is black and white in *your* mind. Others do not distinguish it as
> clearly. Thus, many people see a *very* valid tie-together of SVN and a best
> practices doc for it.
>
> It is fine for /you/ to not want it here, but I think it is a valid topic
> for this list (I'm not speaking authoritatively here; just a +1 on saying
> that the topic is fine for this list). CVS has had *years* to build up a set
> of practices on how to use the thing effectively. SVN is just beginning, and
> we (the people on this list) are the people that are going to flesh out that
> information and those best practices.
If Josef is talking about a best practices that is specific to SVN,
then +1 on talking about it here. (Stuff like "how to arrange
branches in the repository", etc).
But as far as I can tell, he's talking about a generic Best Practices
document that has things like "Format your code in 80 columns." Do
you really think *that* has anything to do with what revision control
system one is using? And furthermore, he's not talking about the
HACKING file, which explicitly limits its domain to the Subversion
project. He's talking about a new document, which claims to be a
guideline for lots of projects, and which is not Subversion-specific.
I haven't seen anyone else on this list who wants to start the same
document Josef is talking about.
What you are +1'ing is not the same thing Josef is proposing (or if it
is, then Josef is not being very clear IMHO).
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Aug 1 23:37:16 2002