You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Isak Johnsson <is...@hypergene.com> on 2002/07/15 16:06:12 UTC
FAQ about global revisions
Quoting the contents of the Subversion FAQ:
> 17. Why does the entire repository share the same revision number? I
> want each of my projects to have their own revision numbers.
Which is what I need to know, but the answer is missing. Can you please
tell me?
If I've got it right, then I'm supposed to put different branches and
major versions in different directories in the same repository. If that
means that they'll have the same revision number, I can't count on the
revision number to know when it's time to rebuild a branch? Nor can I
correlate bug reports by their revision numbers even if the source is
identical.
I guess you have some suggestions on how to do this "the Subversion Way"?
If the revision number really is repository wide then I'd like to use
several repositories instead. I tried, but I couldn't get "svn copy URL1
URL2" to work between repositories. Is this a bug or is it the way it
should be? Is there any other way this should be done?
Thank you in advance!
Isak Johnsson
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: FAQ about global revisions
Posted by Karl Fogel <kf...@newton.ch.collab.net>.
Isak Johnsson <is...@hypergene.com> writes:
> If I've got it right, then I'm supposed to put different branches and
> major versions in different directories in the same repository.
That's right.
> If that means that they'll have the same revision number, I can't
> count on the revision number to know when it's time to rebuild a
> branch? Nor can I correlate bug reports by their revision numbers
> even if the source is identical.
If we knew more concretely what you're trying to do, or the exact
nature of the problems you're anticipating, we might be able to
suggest something. From the above, I'm not really seeing the problem,
thus can't suggest a solution.
You can tell whether or not anything under a given repository path
changed between revisions X and Y (i.e., that path could be "/trunk/"
or "/branches/stable_release_1/" or whatever). Does that you?
> If the revision number really is repository wide then I'd like to use
> several repositories instead. I tried, but I couldn't get "svn copy
> URL1 URL2" to work between repositories. Is this a bug or is it the
> way it should be? Is there any other way this should be done?
Cross-repository copying is not supported in Subversion 1.0.
-K
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: FAQ about global revisions
Posted by Dave Cridland <da...@cridland.net>.
On Mon, 2002-07-15 at 17:06, Isak Johnsson wrote:
> Quoting the contents of the Subversion FAQ:
>
> > 17. Why does the entire repository share the same revision number? I
> > want each of my projects to have their own revision numbers.
> If I've got it right, then I'm supposed to put different branches and
> major versions in different directories in the same repository. If that
> means that they'll have the same revision number, I can't count on the
> revision number to know when it's time to rebuild a branch? Nor can I
> correlate bug reports by their revision numbers even if the source is
> identical.
Rebuilding dependant on the revision is *far* easier than on CVS.
Although a caveat - I don't really understand CVS.
Yes, the repository has a single revision number, which is utterly
fantastic.
Yes, you can rebuild individual directories based on revision number
sanely, I do it all the time:
svn info gives me (for the subversion trunk dir):
Path: .
Url: http://svn.collab.net/repos/svn/trunk
Revision: 2546
Node Kind: directory
Schedule: normal
Last Changed Author: david
Last Changed Rev: 2546
Last Changed Date: Tue, 16 Jul 2002 05:23:22 +0100
Properties Last Updated: Tue, 16 Jul 2002 08:36:50 +0100
Note the "Last Changed Rev:". For automatic rebuilds, that's probably
what you want.
So it's relatively easy to say:
LOCALREV=`svn info --recursive | grep '^Last Changed Rev:' | sed 's/^.*
//' | sort -n | tail -n 1`
(I'm uncertain whether I need the recursive check here - I know at worst
case it'll give me the same version number as a simple svn info, so I'll
do it until someone tells me not to.)
And use that as your local rebuild test. (I check to see if I've built
an RPM with that already, for instance, although this could be done
better.)
Bug report correlation is much the same, although my "feel" is that
seeking out which file was the root cause of the bug is probably vastly
easier with SVN than with CVS, since you actually know what files were
changed between which builds easily, as well as knowing what was
actually in each build.
Dave.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: FAQ about global revisions
Posted by Karl Fogel <kf...@newton.ch.collab.net>.
Isak Johnsson <is...@hypergene.com> writes:
> > 17. Why does the entire repository share the same revision number? I
> > want each of my projects to have their own revision numbers.
>
> Which is what I need to know, but the answer is missing. Can you
> please tell me?
The FAQ has been fixed now, see there.
(Thanks for letting us know!)
-K
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: FAQ about global revisions
Posted by Roman Neuhauser <ne...@bellavista.cz>.
> From: Ben Collins-Sussman <su...@collab.net>
> Date: 15 Jul 2002 14:29:23 -0500
> Subject: Re: FAQ about global revisions
>
> Roman Neuhauser <ne...@bellavista.cz> writes:
>
> > > From: Eric Gillespie <ep...@pretzelnet.org>
> > >
> > > FWIW, i *like* global revision numbers and can't fathom why so many
> > > people dislike or misunderstand them :-/.
> >
> > i didn't like them either at first. but just from reading this list
> > it's obvious how great they are.
>
> Well, I guess that one of the cool things about global revision
> numbers is that every commit (changeset) has a definite name. That's
> why we can so easily talk about "reverting r2504", whereas on other
> projects, people talk about "reverting joe's 11:03am commit last
> tuesday". :-)
just what i was talking about. :)
--
FreeBSD 4.6-STABLE
9:34PM up 2 days, 11:48, 4 users, load averages: 0.02, 0.04, 0.00
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: FAQ about global revisions
Posted by Ben Collins-Sussman <su...@collab.net>.
Roman Neuhauser <ne...@bellavista.cz> writes:
> > From: Eric Gillespie <ep...@pretzelnet.org>
> > To: dev@subversion.tigris.org
> > Date: Mon, 15 Jul 2002 14:12:48 -0500
> > Subject: Re: FAQ about global revisions
> >
> > FWIW, i *like* global revision numbers and can't fathom why so many
> > people dislike or misunderstand them :-/.
>
> i didn't like them either at first. but just from reading this list
> it's obvious how great they are.
Well, I guess that one of the cool things about global revision
numbers is that every commit (changeset) has a definite name. That's
why we can so easily talk about "reverting r2504", whereas on other
projects, people talk about "reverting joe's 11:03am commit last
tuesday". :-)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: FAQ about global revisions
Posted by Roman Neuhauser <ne...@bellavista.cz>.
> From: Eric Gillespie <ep...@pretzelnet.org>
> To: dev@subversion.tigris.org
> Date: Mon, 15 Jul 2002 14:12:48 -0500
> Subject: Re: FAQ about global revisions
>
> FWIW, i *like* global revision numbers and can't fathom why so many
> people dislike or misunderstand them :-/.
i didn't like them either at first. but just from reading this list
it's obvious how great they are.
--
FreeBSD 4.6-STABLE
9:22PM up 2 days, 11:36, 4 users, load averages: 0.03, 0.02, 0.00
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: FAQ about global revisions
Posted by Eric Gillespie <ep...@pretzelnet.org>.
Isak Johnsson <is...@hypergene.com> writes:
> If I've got it right, then I'm supposed to put different branches and
> major versions in different directories in the same repository. If that
How you manage 'branches' is up to you. I don't like the /branches
that the svn repository has. I'm managing my repository so that
each project has at least a 'current' directory, analogous to cvs
HEAD. Releases are copied to /releases/foo/foo-version. 'Branches'
or 'tags' are created as needed along-side 'current'.
> I can't count on the
> revision number to know when it's time to rebuild a branch? Nor can I
I don't understand what you mean here.
> correlate bug reports by their revision numbers even if the source is
> identical.
Nor here.
> If the revision number really is repository wide then I'd like to use
> several repositories instead. I tried, but I couldn't get "svn copy URL1
If you do that, you're not going to be able to share code between
projects. For example, we have buildtools, doctools, and portability
modules shared between all our projects.
FWIW, i *like* global revision numbers and can't fathom why so many
people dislike or misunderstand them :-/.
--
Eric Gillespie <*> epg@pretzelnet.org
Build a fire for a man, and he'll be warm for a day. Set a man on
fire, and he'll be warm for the rest of his life. -Terry Pratchett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org