Question about Source Control

Terry Reedy tjreedy at udel.edu
Tue Mar 18 21:38:06 EDT 2014


On 3/18/2014 5:51 PM, Gregory Ewing wrote:
> Frank Millman wrote:
>> These are the kind of stumbling blocks that prevented me from
>> succeeding in my previous attempt. I have a vague recollection that I
>> set it up on machine A, but then hit a problem because machines B and
>> C both accessed the same directory, but with different names
>
> For dealing with your practice of editing on one machine and
> running on another, you may be best off having just *one* local
> repository, residing on the shared file system. Whichever machine
> you're working on, you cd to the shared directory and use hg or
> git commands from there, so all the pathnames you're using are
> relative.

At least with hg, one should best test the code in the working directory 
*before* committing to the local repository. The one local repository 
could still be a close of a master repository somewhere else. One can 
push multiple commits at once, either as the end of a work session or 
when one has done enough to become paranoid about losing work.



-- 
Terry Jan Reedy




More information about the Python-list mailing list