# How to connect remotely with Git machine

2 messages from 2009-06-08 to 2009-06-08. Participants: stpl_nk, Eric Raible.
Thread: https://gitlist.dev/t/19742

## stpl_nk, 2009-06-08 09:30

Subject: How to connect remotely with Git machine
Message-ID: <23920805.post@talk.nabble.com>
URL: https://gitlist.dev/e/23920805.post%40talk.nabble.com

```

Hello all ,
I am new in using Git . I have a small network , all the machine in LAN . I
install Git in my windows machine (Windows XP sp2) in a central location .
Now how to connect other hosts to central windows machine with the help of
Git .

Thanks .


-- 
View this message in context: http://www.nabble.com/How-to-connect-remotely-with-Git-machine-tp23920805p23920805.html
Sent from the git mailing list archive at Nabble.com.

```

## Eric Raible, 2009-06-08 15:25

Subject: Re: How to connect remotely with Git machine
Message-ID: <loom.20090608T151053-794@post.gmane.org>
URL: https://gitlist.dev/e/loom.20090608T151053-794%40post.gmane.org
In-Reply-To: <23920805.post@talk.nabble.com>

```
stpl_nk <nkjha <at> systematixtechnocrates.com> writes:

> 
> 
> Hello all ,
> I am new in using Git . I have a small network , all the machine in LAN . I
> install Git in my windows machine (Windows XP sp2) in a central location .
> Now how to connect other hosts to central windows machine with the help of
> Git .
> 
> Thanks .

We have a similar situation at $dayjob.
Each developer who is ot use git installs it locally.
Each developer has their own local repo.
The shared (bare) repo is on a network drive, and that drive is mapped:

c:> net use g: \\server1\Engineering

Then individual developers can clone do something like this from bash:

$ git clone file://g:/path/to/repo/on/G

The only real hitch is that (in the largest single fustercluck
or all time) windows likes using backslash as a path separator.

But mapping the network drive to a drive letter allows you to avoid
almost all of the pain.

- Eric

```
