From my own experience, if you already have a repository being managed
by a SVN server (svnserve or mod_svn), you must have all SVN clients
access that repository via the server.
This is the recomended way, anyway.
If you absolutely must allow some SVN clients to directly access the
repository via a file share, then all of the SVN clients must access
it via the file share.
Also, the repositiory must be in FSFS format.
On 3/1/08, Joe Contreras <jscontreras_at_cox.net> wrote:
> Hi,
>
> I'm not sure if this is where you post help for TortoiseSVN 1.4.2.
>
> I'm having issues setting up the checkout - checkin process for TortoiseSVN.
> My scenario.
>
> I have a code base in classic ASP that requires version control. I have SF
> Subversion as the repository and I'm using TortoiseSVN 1.4.2 as the client.
>
> The issue; we have a team that requires these files to be on a shared
> network drive everyone can check them out from the same drive and lock the
> necessary files and unlock them and commit them from this network drive.
> How do we do that using TortoiseSVN? My understanding is that everyone can
> checkout the entire repository and only if you are using that file do you
> need to lock it to avoid conflicts with other team members. Once I get this
> figured out we'll be up and running. I think this is a cool product and
> want to utilize it accordingly. I've used VSS in the past for version
> control however I've never used TortoiseSVN.
>
> All help will be appreciated greatly.
>
> Thank You
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
> For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-03-01 21:13:49 CET