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

Re: the FAQ, and de-emphasizing the whole "project" thing

From: Karl Fogel <kfogel_at_red-bean.com>
Date: Mon, 15 Sep 2008 12:10:24 -0400

I've rewritten the FAQ entry in r33079, based in part on this thread.
The new text is below; it will also be live on the web site in an hour
or so. If it's still unclear, suggestions welcome (real patch format is
the most efficient way to make suggestions, if you can).

---------------------------------------------------------------------------
   Why does the entire repository share the same revision number? I want
   each of my projects to have their own revision numbers.

   First, note that Subversion has no concept of projects. The
   repository just stores a versioned directory tree -- you may consider
   certain sub-trees to be projects, but Subversion doesn't treat them
   differently from any other sub-tree. Thus, the interpretation of what
   constitutes a project in the repository is left entirely up to the
   users. (This is similar to how branches and tags are conventions
   built on top of copies, instead of being basic concepts built into
   Subversion itself.)

   Each time you commit a change, the repository stores a new revision
   of that overall repository tree, and labels the new tree with a new
   revision number. Of course, most of the tree is the same as the
   revision before, except for the parts you changed.

   The new revision number is a sequential label that applies to the
   entire new tree, not just to the files and directories you touched in
   that revision. However, colloquially, a revision number is used to
   refer to the change committed in that revision; for example, "the
   change in r588" ("r588" is shorthand for "revision 588") really means
   "the difference between repository trees 587 and 588", or put another
   way, "the change made to tree 587 to produce tree 588".

   Thus, the advancing revision number marks the progress of the
   repository as a whole; you generally can't gauge the progress of a
   particular project within the repository by watching the revision
   number. Also, the revision number should not be used as the
   publicly-visible release number of a particular project in the
   repository. For that, you should devise some other mechanism of
   distinguishing releases.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-09-15 18:10:48 CEST

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.