On 7/29/05, Jan W. Hentsch <jwh@csmed.de> wrote:
> > But, you might not want to do an update automatically.
> > Sometimes one has mixed revisions because he/she wanted it
> > that way. I have had situations like that.
>
> OK, but we could call my wanted keyword something like "YoungestChild".
> Than the meaning would be clear, even in mixed Workinf directories.
>
> The advantage would be, If I link that information into the code and
> made
> it visible with something like "program --version" I could always say
> what revision the code is/was derived from, and even better, any user of
> my program could tell me what revision he/she is using. So I could easy
> check the same version out to do some investigation to errors the user
> tells
> me.
>
In this situation, the "program --version" would not give the right
information. The user might have foo.c at revision 20 and bar.c at
revision 30. It is a mistake to say that the user's code is at
revision 20. It is also a mistake to say that it is at revision 30.
There can not be one revision representing the whole working copy.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Jul 30 00:50:38 2005