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

Re: Checkout to SAMBA 3.5.6 share

From: Simon Large <simon.tortoisesvn_at_gmail.com>
Date: Thu, 3 Mar 2011 17:38:15 +0000

On 3 March 2011 17:19, Andy Levy <andy.levy_at_gmail.com> wrote:
> Placing WCs on network drives has been discouraged for as long as I
> can remember. It may be possible (with some additional work), but a
> local WC is always the most proper way to set yourself up.

Placing repositories on a network share has always been discouraged
very strongly. Sharing working copies has always been strongly
discouraged too, because it negates the whole point if having revision
control. Placing personal working copies on a network share is not
really discouraged, but it is not exactly supported either due to the
known problems with such devices. I think the general theme is that if
it works for you then all well and good, if it doesn't then all you
can do is try to get some clue from other people who have suffered the
same problem.

Having a local WC is definitely the best way, but there are some
occasions when it is useful to have the WC on a share. My own case a
few years ago is where I had a share on a Linux box. I did all the
editing and version control from Windows (using TSVN) and compiled
under Linux using a PuTTY session. All I can say is that it worked for
me. YMMV.

Simon

-- 
:       ___
:  oo  // \\      "De Chelonian Mobile"
: (_,\/ \_/ \     TortoiseSVN
:   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
:   /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2709351
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-03-03 18:38:22 CET

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.