On Wed, Sep 22, 2010 at 14:40, Nicolas Goutte
> Am 22.09.2010 um 20:07 schrieb Marc Guay:
>> 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.
> You would only need to do an update, not a full checkout (if I
> understand what you mean).
> Also I remember to have read somewhere that a version control system
> does not replace the personal discussion between person. So I would
> suggest that you use a server and as soon as somebody of you two have
> made a commit he/she tells it the other one (by voice, phone, email,
> whatever is easier).
Or just get everyone in the habit of updating their working copies frequently.
> So that way you do not need an automatic email sender in the so-
> called post-commit-hook of your server (with the potential problem
> that email are rather public.)
"Public" emails really isn't a concern here; as I read the OP, it's 2
programmers in the same office of the same company. Intra-office email
between 2 people is not terribly public.
> If you really really do not want a server, you could use the file:///
> protocol but beware of file permissions (as you would write as
> different users) and that you *cannot* use file:/// throught a remote
> file system (or you would risk corruption).
By definition, if you use file:///, at least one person will be using
a "remote" filesystem unless they are both logged onto the same
computer, and that computer also hosts the repository itself.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-09-22 20:54:18 CEST