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

Re: Having working folder located on network drive

From: Craig <shadycraig_at_gmail.com>
Date: Mon, 21 Mar 2011 09:19:10 -0700 (PDT)

On Mar 21, 3:37 pm, Andy Levy <andy.l..._at_gmail.com> wrote:
> On Mon, Mar 21, 2011 at 11:33, Craig <shadycr..._at_gmail.com> wrote:
> > On Mar 21, 10:43 am, Andy Levy <andy.l..._at_gmail.com> wrote:
>
> >> It is neither suggested nor recommended. It is technically *possible*
> >> but not supported. Working copies are meant to be locally-attached
> >> disks.
>
> >> I'm guessing you're using an older version of SAMBA for that network
> >> share.http://tortoisesvn.net/faq.html#samba
>
> >> ------------------------------------------------------http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMess...
>
> > Thanks Andy, but I'm not using Samba.
> > Everything is windows in this system.
>
> Then your permissions on the share are still messed up, or your
> antivirus is interfering.
I'll look into it.

> If this is purely so that changes get backed up without being
> committed, make your WCs local and give each user a private branch to
> commit to regularly. Then merge changes back to trunk (or whatever
> you're using) when ready.
Yes this is exactly the reason.
Although the company is quite new to SVN we are already using branches
for features/bugs, having 'user' branches as well would be over
complicated for our situation.

Ideally software fit around my workflow, rather than having me adapt
to it's (like having to commit to backup), but if there underlying
layers are not up to the job then so be it.

Thanks for the help,
Craig

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2712937

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