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

Re: setting up a repo for GUI browsing

From: Jeff Smith <jsmith_at_robotronics.com>
Date: 2007-03-28 00:27:00 CEST

On Wednesday 07 March 2007 17:00, mansour77@yahoo.com wrote:
> when I commit a file in any project the hole repo's
> revision number changes. My projects are not related to each other,
> and I need each of them to have it's own rev#, history...etc.

Like Mark Phippard mentioned, the fact that multiple projects take
"revision numbers" from the same pool should be no problem. I was a
little taken back when I realized it was the case, but why should it
matter enough for anyone to actually go out and ask for advice?
(Please do post if there is some reason I am missing)

This is my advice; I believe you can rely on these points:

* In any one project, the higher revision number will always be the
newer revision, i.e. r56 came after r53. Don't worry that r54 and r55
are not of this project but a different one.

* 'svn log wc/path' will only show you the revisions relevant to that
path. Other procedures such as merge also have no trouble because
they are aware of what revisions affect the path you are working

* It is indeed an advantage that r54 is of only one of those projects,
at least once you accept the fact.

* The only reason I thought of that you want rev numbers for one
project to be consecutive is that you want to guess what rev# is
next. That is a bad practice anyway. As you get more users committing
whenever they are ready, you must not assume what rev# you are
committing, until the commit is complete.

Don't forget to 'svn up' before inspecting your local working copy to
see what rev# was committed.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Mar 28 00:27:58 2007

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.