[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-29 23:59:21 CEST

> From: Florian Weimer [mailto:fw@deneb.enyo.de]
> Sent: Friday, July 29, 2005 11:48 PM
> To: jwh@csmed.de
> Cc: users@subversion.tigris.org
> Subject: Re: Global Revision keyword, again and again
> * Jan W. Hentsch:
> > So why not make it practicable, just define one singele file
> > ".svn-version" in the projects main folder that gets updated on
> > checkout/export (maybe on confirm is better). That's all I'm looking

> > for, and I guess, that's all the others are looking for as well.
> The trouble is that the working copy is often in a mixed
> state. Some files might be at revision 345, others at 347,
> and so on. (Basically, this happens after each commit.) A
> single file cannot properly reflect this, especially if it
> just contains a single number.

that is something I just figured out, but after a svn update the
revision of the "Project directory" is correct, so maybe that is
the right point to do the trick.

So whenever I would do a svn commit, I would follow it with an svn

what do you think?

thanks in advance, vielen Dank schon mal,

cu jwh

Jan W. Hentsch, jwh@csmed.de
CSMed GmbH
Otto-Röhm-Straße 69
64293 Darmstadt
Mobile: +49 172 65 11 487

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:00:22 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.