[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Global Revision keyword, again and again

From: Jan W. Hentsch <jwh_at_csmed.de>
Date: 2005-07-30 00:50:42 CEST

> >
> > 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
revision out to do some investigation to errors the user/customer tells

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

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.