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

Re: Best Practices (was: rapidsvn feedback)

From: Karl Fogel <kfogel_at_newton.ch.collab.net>
Date: 2002-08-01 21:10:29 CEST

Josef Wolf <jw@raven.inka.de> writes:
> > No, *not* in the svn repo. In its own repo. New document, new
> > project. Not related to Subversion.
> Ummm. Do we really want to run an own repo for just a couple of pages?

I see I'm not getting through, here :-).

This is not "we". This document is *your* project (plus anyone else
who wants to join you). It is not part of the Subversion project, and
should not be discussed nor developed here.

Josef, I'm sorry to keep posting saying the same thing. But what I
want to avoid is this list getting swamped with mails about generic
Best Practices (a topic which is sure to generate huge, noisy

> But maybe you are right and it would actually get a lot of pages, so
> it would make sense to separate it. So give me some days to put the
> pieces together and _then_ determine whether/where we want to put the
> result.

Put it anywhere you want, as long as it's not the Subversion

Sigh. I'm genuinely frustrated at my inability to make this clear:

Imagine you were starting a new project, to write a GUI for
controlling satellites in orbit. You're looking for a place to put
that project. Now, *why* would you post on the Subversion dev list to
discuss the project and where to put it?

You wouldn't, because it's a different project, of course.

THAT's the situation you're in with this document.

So ***please*** stop posting about it here, okay?


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Aug 1 21:25:32 2002

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.