If you are on an internal 'local (file) network' I would expect that you can 
simply use the URL that you would use to look at the same folder with Win 
Explorer, e.g. \\PC-3\OtherGuy\HisRepo (note this uses the windows backslash 
separator)  I use this method with Git Extensions and Git for Windows (msysgit 
compiled) at work. It doesn't need usernames or passwords as teh permissions 
are done by the file system.

If you are accessing via an intranet, or are using Cygwin then the linux style 
is more likely, and don't forget to munge (adjust) the colon in "C:"
  ----- Original Message ----- 
  From: Leonidas Savvides 
  To: Philip Oakley 
  Sent: Sunday, April 07, 2013 6:43 AM
  Subject: Re: [git-users] connectng 2 win PCs in local network - clone folder 
to other PC


  YES IT HELPS... 
  I CLONE COMMAND should be like this or...


  git clone User-HP@192.168.10.11:C:/Users/User/Documents/PhoneGap/trnotes 
theProject


  trnotes dir from which to send - source
  theProject  receive dir / from this executed in CLI - destined


  User-HP@192.168.10.11    username of SOURCE PC and LAN IP



  WELL IS CORRECT?




  On Sat, Apr 6, 2013 at 4:51 PM, Philip Oakley <philipoak...@iee.org> wrote:

    From nothing.
    Simply start with `git init` on the first PC. (and `git add`; `git commit` 
etc. so you have something in the repo)
    Permit sharing.
    Got to second (or third, 4th, ..) PC, create directory, permit sharing, and 
then `git clone`. This should populate the directory with the 'copy' of the 
remote PC-1.
    Create and checkout your development branch for that PC-n.
    Note that you do not have a central bare repository machine. All your 
remotes are working machines, so there is a potential for collision if one 
person tries to push a branch that is checked out (and possibly dirty with 
in-work, uncommitted changes) on the remote machine. I believe git will refuse, 
but I'm not sure.

    You can now 'push' that branch back to PC-1, and 'fetch' from PC-1 any work 
they did. Like wise you can push work from PC-2 to PC-4 if they are want to 
exchange work on a feature they are working on (and fetch back)

    I would advice never to 'pull' in this situation as it attempts an auto 
merge, but to do a distinct two step of 'fetch' and then 'merge'. It gives you 
a breathing space just in case. (option to require it to be a ff, and clean 
tree?)

    Designate one machine as the location of the primary reference for which 
ever branch you end up using as "master", and set up some admin to stage those 
updates gracefully with team emails to notify when updates are in place.


    Does that help?

    ----- Original Message ----- From: "Leonidas Savvides" 
<lsepolis...@gmail.com>
    To: <git-users@googlegroups.com>
    Sent: Saturday, April 06, 2013 2:07 PM
    Subject: Re: [git-users] connectng 2 win PCs in local network - clone 
folder to other PC




      What command to use for the push / copy?

      Also both directories must have .git folder... Initialized with git?

      Source PC is win7, and destined PC vista both 64bit.....

      -- 





  No virus found in this message.
  Checked by AVG - www.avg.com
  Version: 2013.0.3272 / Virus Database: 3162/6228 - Release Date: 04/06/13

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to