Re: [TSVN] SubWCRev update

Molle Bestefich wrote:
> Simon Large wrote:
>>> Thanks for explaining, you're right.
>>> I come from a VS.Net / NetBeans etc. world where builds are done
>>> with the click of a button in the GUI, and SubWCRev doesn't lend
>>> itself to this way of working very easily. The Subversion way of
>>> doing keywords work better there.
>>
>> But the SVN substitution is done at update time so it won't find
>> local mods made after that. You have to run a program at the time
>> you want to make that check.
>
> At commit also, no?

Well OK. But what if you build before committing?

> I'm unsure what local modifications you'd like to find and include in
> a build that's not reflected in the repository somehow, but I'll go
> read the docs again.

Some people (including me) use it in their build scripts for exactly
that reason. We _don't_ want to release uncommitted code by mistake, and
using SubWCRev helps show that condition up. It is all too easy to
commit changes and then forget to redo the build before making the
release.

Simon

-- 
       ___
  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