On Jun 17, 2005, at 10:02 AM, Servico Tpd Rodrigo Alfonso Menezes
> Are you serious that the
> Project1 programmers can freely change the Project45 revision?
There is no "project" revision. There is a repository revision.
Someone checked stuff into the repository so the revision number was
changed. In Subversion there is no such thing as a revision number
attached to a project - only the state of the repository tree. The
HEAD revision may be different, but you can still look at Project45
and say our milestone was reached at revision N of the repository..
the fact that other projects bump the revision doesn't change the
usefulness of the previous revision numbers.
> I donīt see
> any meaning here. Even if you say: "Hey, itīs a technical gory
> deatil so
> you donīt have to use dates." Ok. I buy it. But does it make sense
> 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
> Project45 have gone wild in their nightly work, but why the heck
> that mess with me?
But it DOESN'T mess with you. You are still attaching meaning to the
revision number that is not there.
> Project45 is a Web page, they commit every second. And
> as an organized person, I preffer to know that my project increases
> "not-to-be-considered" release as a helper, and not an exposed
> piece that we should share among all... I know it shouldnīt be used
> and de
> industry standard code growth indicator, but it helps... it really
> To me, sharing it with other projects is like sharing your wife
> with your
you can get a log of only the folder within the repository that
contains your project then, not the root of the repository. Then you
will only see the changes that happened to your project.
If you wish, you can use hook scripts to notify you when changes are
made to a particular path within the repository.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Fri Jun 17 17:22:43 2005