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

RE: 2 users sharing same working copy

From: Bob Archer <Bob.Archer_at_amsi.com>
Date: Thu, 23 Sep 2010 11:24:08 -0400

> I started using TortoiseSVN as a simple way to keep track of my
> changes to source code while working as a one-person team. I have
> a
> single repository with many directories, each of which contains a
> project. The repository and working files are located on my hard
> drive. We recently hired a second developer and I have shared my
> working files with her. Up until now, I've monitored the changes
> she's made and committed them myself. She cannot see the status of
> the files from her PC, even though TortoiseSVN is installed. I
> would
> like her to be able to commit her own changes and be able to see
> which
> files have been modifed and which not.
>
> I understand that it's probably more to the point of the software
> to
> set up a server and have her checkout her own working copy and
> commit
> her changes to the repo but in my mind it's overly complicated for
> our
> purposes. (We would each have to verify that the other had not
> made
> changes and checkout a fresh copy every time we did any work on a
> project?). I set up the server and had this working so don't think
> it's out of laziness or ignorance that I'm not into it.
>
> Any advice is nice,

Frankly setting up svnserver to run as a service on your PC will take you no more than 30 minutes following the red-book directions.

Or, even simpler share out your repository and your co-worker can check out from there.

Sharing a working copy is more work than any or all of the above.

BOb

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

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-09-23 17:24:20 CEST

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.