While impersonating an English Lit major,
Servico Tpd Rodrigo Alfonso Menezes Madera wrote:
> But does it make sense that yesterday you were working with
> revision 342 of Project2 and suddenly today in the morning
> you are working with revision 784? I mean, the guys from
> Project45 have gone wild in their nightly work, but why the
> heck should that mess with me? Project45 is a Web page,
> they commit every second. And as an organized person,
> I preffer to know that my project increases itīs
> "not-to-be-considered" release as a helper, and not an
> exposed technical piece that we should share among all...
I also had more than a little pain getting my mind to accept
the concept behind this.
I think the point that may be somewhat hidden to you is that
Project2 is not at revision 784.
The *repository* is at revision 784. You may check out the
latest version of Project2 by checking out that folder in
either revision 342 of the repository or revision 784 of the
repository. (Although, to reduce your pain it would be better
to check out the head revision - unless you need a specific
historical revision).
So, what is the version of your Project2? Whatever you want it
to be - preferably through a copy to the tags folder:
Project2-AlmostWorks
Project2-V1.08
Project2-V1.09-Toxic
Project2-V1.45-RC1
Etc. Obviously there is little point in tagging every commit. If
you are overly concerned - having observed an unexpected repository
revision jump - a *log* or *blame* will quickly tell you what is going
on.
Having said all that, I often set up separate repositorys for separate
projects when they are wildly unrelated - primarily for ease of backups
and security maintenance. (Hello Enron? Thank you *so* much for SarbOx...)
xev
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jun 17 17:17:57 2005