Re: Rapidly-changing revision number (was: First-time user (Windows platform))

On Fri, 2006-10-13 at 11:43 -0700, Kenneth Porter wrote:

> > Wasn't there recently an argument here for multiple repositories, on the
> > basis that working with revisions can get annoying when the entire
> > repository (and thus every "project" in it) gets a new revision every
> > time something changes?
>
> "Annoying"? That's hardly a good technical argument. (I realize you're
> quoting a previous thread and that it's not your argument.)
>
> The revision is not unlike a timestamp. Would one complain that every
> check-in has a unique timestamp?

Yes, I'd expect people to complain if timestamps changed on files
that weren't related to the one(s) that changed.

> In other file-oriented systems, one checks out a previous snapshot of a
> part of the database using a timestamp. In Subversion, one grabs that same
> snapshot by revision number. I find the revision number more accurate and
> reliable.

What does that mean in the context of putting unrelated projects
under the same repository? If you combine them, the repository
version number is going to change on projects where no change
took place. It probably doesn't really matter, since you normally
either check out the HEAD, not caring about the version number or
you create a tag if a specific version matters.

-- 
  Les Mikesell
   lesmikesell@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org