> -----Original Message-----
> From: Aaron Martinez [mailto:ml_at_proficuous.com]
> Sent: 03 December 2008 15:45
> To: Giulio Troccoli
> Cc: 'Aaron P. Martinez'; users_at_subversion.tigris.org
> Subject: RE: reposity versioning
> > Linedata Services (UK) Ltd
> > Registered Office: Bishopsgate Court, 4-12 Norton Folgate, London, E1
> > Registered in England and Wales No 3027851 VAT Reg No 778499447
> > -----Original Message-----
> >> From: Aaron P. Martinez [mailto:ml_at_proficuous.com]
> >> Sent: 03 December 2008 15:18
> >> To: users_at_subversion.tigris.org
> >> Subject: reposity versioning
> >> Hi All,
> >> I have developers who I maintain subversion for and they have one
> >> repository that they call "core", this is the base of many new
> >> When they start on a new project they would like to start that project
> >> at
> >> revision 1.0 but I'm not sure how to copy the core to a new repository
> >> and
> >> get the revision numbers back down. Is this even possible?
> > No, you cannot "reset" the revision if you keep the project in the same
> > repository.
> > You can, however, create a new repository, check it out to a working
> > (which would be at revision 0), copy your "core" project in this WC, and
> > import it into the repository (or add and then commit). This will create
> > revision 1.
> > Anyway, why is it important? The revision is just a number, you, or your
> > developers, should not give it any special meaning.
> > Giulio
> > ------------------------------------------------------
> > To unsubscribe from this discussion, e-mail:
> > [users-unsubscribe_at_subversion.tigris.org].
> Thanks Giulio,
> We wouldn't be keeping the same reposity, for every new project i create a
> new repository. I think the checking out from core and then importing to
> the new repository is what will do the trick.
I dind't say checking out from core. I said copying, meaning copying with the OS command (not svn cp command).
> I agree about the revision numbers. I think they are more concerned about
> "version" numbers. They always want the new project to start at version
> 1.0, if that has any bearing. That being said, i'm not a developer so I'm
> still trying to get a handle on the whole process and they aren't the best
> at describing what they want. I think this will work fine for what I need
If they actually meant "version 1.0" rather than "revision", maybe it would simpler to keep everything in one repository and use the tags instead. You create a new project copying (this time with svn) the core, then create the usual structure of branches and tags and then, I you really want, you create the first tag, called 1.0. Something like the following
svn mkdir <URL to new project> -m"Creating new project blah blah"
svn copy <URL to core> <URL to new project>/trunk -m"Copying core"
svn mkdir <URL to new projct>/branches -m"Creating branches"
svn mkdir <URL to new project>/tags -m"Creating tags"
svn copy <URL to new project>/trunk <URL to new project>/tags/1.0 -m"Tagging version 1.0)
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2008-12-03 17:05:42 CET