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

Re: one more example of unclear terminology in SVN book

From: Robert P. J. Day <rpjday_at_mindspring.com>
Date: 2004-12-19 22:04:41 CET

On Sun, 19 Dec 2004, Ben Collins-Sussman wrote:

> Hm, okay. Perhaps we should exise the word 'project' from all of
> the early chapters. Subversion has no concept of 'project' at all,
> just directories. Perhaps we should just standardize on the phrase
> "check out part of a repository".

actually, having whined about this, i'm not sure you really need to
delete the word "project" entirely, so much as emphasize early on that
it's strictly an informal term that is commonly applied to, say,
top-level directories in a repository that folks might find it useful
to check out independently. kind of a loose, shortcut terminology,
but having *no* official meaning in the context of svn.

and, personally, i think it would have been handy to have seen
something like Figure 4.2 earlier, showing the calc and paint
directories with their own "trunk/" and "branches/" subdirectories.
*that* picture goes a long way to graphically depicting how to break a
repo into separate (dare i use the word?) "projects". :-)


p.s. based on what i've seen so far, i'm assuming you can introduce
the trunk/tags/branches at any arbitrary subdirectory level where you
think folks might want to be creating branches and doing tagging, yes?

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Dec 19 22:07:51 2004

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

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