Re: Forcing Update Before Commit

joseph.h.dayney@rrd.com wrote:
>
> Our Development Group was wondering if there is a way to configure
> TortoiseSVN (SubVersion) to "FORCE" a Working Copy Update, before a
> Commit takes place ... to prevent inadvertantly wiping out previously
> committed changes because an UPDATE did not occur prior to the COMMIT.
> If it is possible, we would like THIS to be the DEFAULT configuration.

How did you manage to wipe out previously committed changes? If the
working copy is out of date, the commit will fail.

And if the update pulls down changes which get merged into your WC,
perhaps you should be checking that there are no conflicts and making
sure the build still works before going ahead and committing.

Simon

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org