[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Forcing Update Before Commit

From: <joseph.h.dayney_at_rrd.com>
Date: 2006-11-28 01:03:52 CET

Hi Simon,

Thanks for your response. You are absolutely correct. We have 2 possible
scenarios that we are looking at. One is where someone does an Update with
SVN, but then copies in a change from another platform, ie UNIX to
Windows. Since the Update Synch'd the Windows Working Copy with SVN, it
would not pick up the out-of-date condition ? The other involves a
Branch-Merge operation which does take careful Human analysis and
verification prior to a commit. In either case, an Update would have
caught the problem but I guess in retrospect, these are conditions outside
of the "NORMAL" operations and SNV can not catch every possibility.

Best Regards,

Joe

Joseph H. Dayney
Contract Software Engineer
Excel Resources
AppDev Team

435.755.4278 Office
801.608.1052 Cell
435.755.4210 Fax
801-272-6615 SLC Home
joseph.h.dayney@rrd.com

Moore Wallace, An RR Donnelly Company
630 W 1000 N
Logan, UT 84321

CONFIDENTIALITY NOTICE: The information contained in this email message
is confidential and may be protected from disclosure. Please be aware
that any unauthorized use, printing, copying, disclosure or dissemination
of this communication may be subject to legal restriction or sanction. If
you think you have received this email message in error, please reply to
sender.

Simon Large <simon@skirridsystems.co.uk>
11/27/2006 03:44 PM
Please respond to dev
 
        To: dev@tortoisesvn.tigris.org
        cc:
        Subject: 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
Received on Tue Nov 28 01:04:16 2006

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.