GIT clone repo across local file system in windows

Question

I am a complete Noob when it comes to GIT   I have been just taking my first steps over the last few days   I setup a repo on my laptop  pulled down the Trunk from an SVN project  had some issues with branches  not got them working   but all seems ok there   I now want to be able to pull or push from the laptop to my main desktop   The reason being the laptop is handy on the train as I spend 2 hours a day travelling and can get some good work done   But my main machine at home is great for development   So I want to be able to push   pull from the laptop to the main computer when I get home   I thought the most simple way of doing this would be to just have the code folder shared out across the LAN and do   git clone file   192 168 10 51 code   unfortunately this doesn t seem to be working for me   so I open a git bash cmd and type the above command  I am in C  code  the shared folder for both machines  this is what I get back   Initialized empty Git repository in C  code code  git  fatal   C  Program Files  x86  Git code  does not appear to be a git repository fatal  The remote end hung up unexpectedly   How can I share the repository between the two machines in the most simple of ways   There will be other locations that will be official storage points and places where the other devs and CI server etc will pull from  this is just so that I can work on the same repo across two machines   As per Sebastian s suggestion I get the following   C  code gt git clone --no-hardlinks file   192 168 10 51 code Initialized empty Git repository in C  code code  git  fatal   C  Program Files  x86  Git code  does not appear to be a git repository fatal  The remote end hung up unexpectedly     EDIT - ANSWER     Thanks to all that helped   I tried the mapping a drive and that worked so thought I would go back and retry without mapping   The final result was   git clone file       192 168 0 51 code   This worked great   Thanks

User · Answer

Not sure if it was because of my git version (1.7.2) or what, but the approaches listed above using machine name and IP options were not working for me. An additional detail that may/may not be important is that the repo was a bare repo that I had initialized and pushed to from a different machine.

I was trying to clone project1 as advised above with commands like:

$ git clone file:////<IP_ADDRESS>/home/user/git/project1
Cloning into project1...
fatal: '//<IP_ADDRESS>/home/user/git/project1' does not appear to be a git repository
fatal: The remote end hung up unexpectedly

and

$ git clone file:////<MACHINE_NAME>/home/user/git/project1
Cloning into project1...
fatal: '//<MACHINE_NAME>/home/user/git/project1' does not appear to be a git repository
fatal: The remote end hung up unexpectedly

What did work for me was something simpler:

$ git clone ../git/project1
Cloning into project1...
done.

Note - even though the repo being cloned from was bare, this did produce a 'normal' clone with all the actual code/image/resource files that I was hoping for (as opposed to the internals of the git repo).

User · Answer

While UNC path is supported since Git 2 21  Feb  2019  see below   Git 2 24  Q4 2019  will allow  git clone file   192 168 10 51 code   No more file     xxx   file     is enough to refer to an UNC path share  See  Git Fetch Error with UNC      Note  since 2016 and the MingW-64 git exe packaged with Git for Windows  an UNC path is supported   See  How are msys  msys2  and MinGW-64 related to each other     And with Git 2 21  Feb  2019   this support extends even in in an msys2 shell  with quotes around the UNC path    See commit 9e9da23  commit 5440df4  17 Jan 2019  by Johannes Schindelin  dscho   Helped-by  Kim Gybels  Jeff-G    Merged by Junio C Hamano -- gitster -- in commit f5dd919  05 Feb 2019     Before Git 2 21  due to a quirk in Git s method to spawn git-upload-pack  there is a problem when passing paths with backslashes in them  Git will force the command-line through the shell  which has different quoting semantics in Git for Windows  being an MSYS2 program  than regular Win32 executables such as git exe itself   The symptom is that the first of the two backslashes in UNC paths of the form   myserver folder repository git is stripped off   This is mitigated now      mingw  special-case arguments to sh      The MSYS2 runtime does its best to emulate the command-line wildcard expansion and de-quoting which would be performed by the calling Unix shell on Unix systems       Those Unix shell quoting rules differ from the quoting rules applying to Windows  cmd and Powershell  making it a little awkward to quote command-line parameters properly when spawning other processes       In particular  git exe passes arguments to subprocesses that are not intended to be interpreted as wildcards  and if they contain backslashes  those are not to be interpreted as escape characters  e g  when passing Windows paths       Note  this is only a problem when calling MSYS2 executables  not when calling MINGW executables such as git exe  However  we do call MSYS2 executables frequently  most notably when setting the use shell flag in the child process structure       There is no elegant way to determine whether the  exe file to be executed is an MSYS2 program or a MINGW one    But since the use case of passing a command line through the shell is so prevalent  we need to work around this issue at least when executing sh exe       Let s introduce an ugly  hard-coded test whether argv 0  is  sh   and   whether it refers to the MSYS2 Bash  to determine whether we need to   quote the arguments differently than usual       That still does not fix the issue completely  but at least it is something       Incidentally  this also fixes the problem where git clone   server repo failed due to incorrect handling of the backslashes when handing the path to the git-upload-pack process       Further  we need to take care to quote not only whitespace and backslashes  but also curly brackets    As aliases frequently go through the MSYS2 Bash  and as aliases frequently get parameters such as HEAD  yesterday   this is really important    See t t5580-clone-push-unc sh

User · Answer

I was successful in doing this using file     but with one additional slash to denote an absolute path   git clone file    cygdrive c path to repository    In my case I m using Git on Cygwin for Windows  which you can see because of the  cygdrive c part in my paths  With some tweaking to the path it should work with any git installation   Adding a remote works the same way  git remote add remotename file    cygdrive c path to repository

User · Answer

Maybe map the share as a network drive and then do  git clone Z     Mostly just a guess  I always do this stuff using ssh   Following that suggstion of course will mean that you ll need to have that drive mapped every time you push pull to from the laptop   I m not sure how you rig up ssh to work under windows but if you re going to be doing this a lot it might be worth investigating

User · Answer

You can specify the remote   s URL by applying the UNC path to the file protocol  This requires you to use four slashes   git clone file      lt host gt   lt share gt   lt path gt    For example  if your main machine has the IP 192 168 10 51 and the computer name main  and it has a share named code which itself is a git repository  then both of the following commands should work equally   git clone file     main code git clone file     192 168 10 51 code   If the Git repository is in a subdirectory  simply append the path   git clone file     main code project-repository git clone file     192 168 10 51 code project-repository

User · Answer

the answer with the host name didn t work for me  but this did       git clone file     home git repositories MyProject git

User · Answer

After clone  for me push wasn t working   Solution  Where repo is cloned open  git folder and config file   For remote origin url set value    remote  origin       url   file    C  Documentation git server kurmisoftware

User · Answer

git clone --no-hardlinks  path to repo   The above command uses POSIX path notation for the directory with your git repository  For Windows it is  directory C  path to repo contains  git directory    C  some dir  gt  git clone --local file    C  path to repo my project   The repository will be clone to C  some dir my project  If you omit file     part then --local option is implied

User · Answer

Either enter absolute paths or relative paths  For example the first one below uses absolute paths    this is from inside the folder which contains the repository and the backup as subfolders  also remember that the backup folder is not modified if it already contains anything  and if it is not present  a new folder will be created     git  git clone --no-hardlinks   git git test1      git bkp repos   The following uses relative paths     git  git clone --no-hardlinks git test1    bkp repos2

[windows] GIT clone repo across local file system in windows

Examples related to windows

Examples related to git

Examples related to git-clone