[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: Robin Guest <robin.guest_at_gmail.com>
Date: Thu, 3 Mar 2011 13:48:50 +0000

On 3 March 2011 13:42, Felix <fb_at_ltec.ch> wrote:

> On 03.03.2011 14:12, Jean-Marc van Leerdam wrote:
> > Hi,
> >
> > On 3 March 2011 13:59, Wolfgang Rohdewald<wolfgang_at_rohdewald.de> wrote:
> >> On Donnerstag 03 März 2011, Felix Saphir wrote:
> >>>> Can anybody give me hint about what I should try next,
> >>>> including changing a setting of the SAMBA server that is
> >>>> probably known to create trouble with Tortoise SVN?
> >>>
> >>> Simple: Don't do that. Don't put working copies on network
> >>> shares and don't share working copies between operating
> >>> systems.
> >>
> >> I am doing that since a while now and I never had any
> >> problems at all. Mounting a windows 7 system on Linux
> >> and using Linux svn for manipulating the windows files.
> >>
> >> Same with sshfs for manipulating remote working
> >> directories over the internet - slow but no problems.
> >>
> >> So what are the risks? Are they Tortoise-specific?
> >>
> >
> > The risks is: cross platform client interoperability is not guaranteed
> > by the subversion developers. Each platform has its own client
> > implementation and Working Copy formats are not necessarily the same.
> >
> As I said: I do not share working copies between different platforms.
> They reside on a network share to make sure they get backed up. I do not
> use SVN as backup system and therefore some time my pass between two
> commits. During this time my working copy gets backed up daily. A real
> risk would be not to backup the working copy...
> > And working copies are intended to be run off local file systems,
> > network file systems (like samba) sometimes lack features that are
> > used by the subversion libraries. As you have seen, sometimes it works
> > with some versions, only to break when the network file system drivers
> > are updated.

Sorry, ignore my previous advice, you are trying to work with remote working
copies, not repositories.

Still, you shouldn't do it. If you think you need to, your workflow is
broken. If you think you cannot commit regularly because you will corrupt
trunk, then look at using feature branches.

If you still think you need to, remote working copies are still a no-no.
Make your local working copies local, and look at using robocopy or rsync to
mirror your local working copy to a backup location.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-03-03 14:48:53 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.