On 10/05/07, Jon Daley <tortoise@jon.limedaley.com> wrote:
> On Thu, 10 May 2007, Lübbe Onken wrote:
> >> Uooou! Niceee! I really didn't think is possible from the
> >> client! Thanks a loot!
> >> I still have a question though: It's possible to write the revision
> >> incremented: like $WCREV$+1 or something, cause I want to make when
> >> you
> >> click Commit, to
> >> first call this app to write the rev in a file in the
> >> repository, then call the
> >> actual commit, and so, if i just put $WCREV$, the revision
> >> will be always one
> >> behind.
> >
> > Why would you want to do this? There's absolutely no need to store the
> > revision of a file manually inside the file. The $Rev$ keyword takes care of
> > this. It is expanded to the correct value when the file is checked out.
> And what happens after you check in another file? The $Rev$
> keyword is not touched in your version.h file. That is why you need a
> script (as far as I know - I would be glad if there was another way -
> particularly since one place I would use it is in my php project, where
> there isn't a build script, so the version.php has to be manually edited)
The fix for this is in TSVN 1.5 (wait until later this year, or try a
nightly build) which includes client-side hooks. You could use one of
those to call a script automatically.
Simon
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Thu May 10 15:06:31 2007