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

Re: accessing an external-HD repo via windows

From: Kevin Hennessy <perk_at_theabsurd.org>
Date: Tue, 29 Jan 2008 06:59:31 -0800

Simon Large wrote:
> Hang on ... alarm bells. Are you using Windows or cygwin? You cannot
> mix and match with working copy. Either you access it using Cygwin or
> you access it using Windows, but not both. It *will* get corrupted.
>
>

no no.... just using Tortoisesvn. I'm only using cygwin to try to
understand my file permission problem.

> I think you are confusing repo and working copy. Just because the
> repository is 30GB doesn't mean the working copy will be. You
> checkout/update/commit a WC not a repository.
>

I understand. I see myself checking out my entire repo on a new
computer now and then. That's why I'm looking for ways to avoid the 30
Gb download.
> Leave the repo on your laptop with svnserve running. Checkout a
> working copy onto the new computer, don't make a copy of the repo or
> you will have multiple master repos with different content.
>

OK! I like it. I'll play around with it today. I assume there's a
standalone svnserve for windows and that I can check-in/check-out
to/from the sever-laptop over windows-shares, a mounted network drive,
or something like that. I'll def. read up on it.

Thanks for getting me on the right track.... I'm brand new to SVN, but
I'm pretty sure it's heaven.

Hey, anyone know of a networked-attached-storage unit coming online that
could support SVN natively? That would be a cool gizmo. It'd be like
my HD idea, but work.

perk

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-01-29 16:02:48 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.