Molle Bestefich wrote:
> Whoop-ti-doo.
>
> Just got a complaint from a co-worker.
>
> He's using the $Rev$ feature of Subversion.
> He's used to using CVS and, I guess, WinCVS.
>
> In CVS, when he checks in something with an automatic keyword on it,
> his file is updated in his working copy to reflect the new version
> number assigned.
>
> So the process he's using is:
> - develop something
> - test it
> - check it in
> - compile a installer / package / .exe / whatever
>
> Doesn't work with our Subversion setup, because whenever something is
> commited through TSVN, the local copy doesn't receive the update to
> the $Rev <blah blah>$ field. So everytime he commits something, he
> has to do an update afterwards.
>
> Would it be possible to add a feature to TSVN to automatically update
> anything commited, if it commits successfully ?
What does he use the $Rev keyword anyway? In Subversion, that keyword
reflects the "last committed revision", i.e. the revision in which that
file last was committed. It doesn't reflect the revision of the repository!
Usually people want the revision of the repository, and that's what the
SubWCRev.exe tool is for (see the download page).
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed Mar 9 17:23:55 2005