> >
> > So whenever I would do a svn commit, I would follow it with an svn
> > update.
> >
> > what do you think?
> >
>
> 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/customer of my program
could tell me what revision he/she is using. So I could easy check the
same
revision out to do some investigation to errors the user/customer tells
me.
I know, that is what normally Releases (tags like 3.1.17) are good for,
but what
is the problem in having a bit more information?
cu jwh
---------------------------------------------------------------------
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:52:16 2005