Re: [TSVN] Non SVN or TSVN specific revprops

"Simon Large" <slarge@slarge.plus.com> writes:

> The line I have taken in our docs is this: if projects are related,
> perhaps because they are released as a set, like TortoiseSVN,
> TortoiseMerge, SubWCRev, etc. or if they share common data, then it
> makes a lot of sense to keep them together. If they are completely
> unrelated, then it makes sense to separate them.

That is, in my opinion, the most sane proposal. (And one that we
mention in the Subversion book.)

> Why, for example, did you split the SVN book out of the main SVN
> repo?

Bad example. In this case, it was not really a technical decision.
It was done mostly because the license and copyright on the book
differed from that of the rest of Subversion. Also, I wanted to bind
the book more closely with "red-bean.com" than with "collab.net" or
"tigris.org". Stuff like that.

> In Brad's case, 500 projects in 1 repository sounds a bit unwieldy.

Maybe he should consult with the ASF infrastructure team. They're
doing the all-projects-in-one-repository, as well as the migrate-a-
project-at-a-time-from-CVS thing. Very similar to his situation.

> Are these projects all live? Are they all related?

Well, they're related in that they share a server. ;-) (I know, I
know...)

> But in the end it is just as personal as how you organise your
> directory hierarchy on your computer. Some people like deep
> hierarchies, some like flat ones.

Agreed.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed May 25 22:36:08 2005