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

Re: Disabling overwriting of existing files in wc on update

From: Alexander Iljin <ajsoft_at_yandex.ru>
Date: Thu, 30 Aug 2012 13:38:18 +0400


>>  now that we start to really use SVN some colleagues demanded
>>  yesterday that a update should never simply overwrite any already
>>  existing file in the working copy. In such a case it should (as can
>>  be configured for file conflicts already) show this as a conflict
>>  which has to be manually resolved.

> Canonical answer: Tortoise SVN like any other VCS cannot replace human
> communication. Make your developers talk to each other. Then you don't
> have to invent (quirky) solutions for nonexistent problems. An update is
> supposed to change files, conflicts should be avoided.

  Case: I've got some unversioned files in my WC, which I keep for myself.
  Someone else somewhere added a file with a matching name and committed.
  When I run "Update" - BOOM - my files are gone, replaced with someone
  else's, no questions asked.

  I just tested, and that's exactly how it worked.

  Felix, an I right in interpreting your suggestion as follows:
  - Whenever you add new files, notify all your coworkers beforehand and
    provide a list of added files so they make sure they don't have
    anything unversioned of the same name in their WCs.
  - And (in case someone forgot so send such notification) whenever you
    run "Update" manually check in advance that there are no new files
    to be expected.

  Why on earth does a VCS not guarantee safety of user data?

  I especially liked this part:

> conflicts should be avoided.

  Yeah, right. Also, everyone should work on separate sets of files and never overlap.



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-08-30 11:38:28 CEST

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

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