# git via rsync

2 messages from 2007-04-20 to 2007-04-21. Participants: Julian Phillips, Rogan Dawes.
Thread: https://gitlist.dev/t/7761

## Julian Phillips, 2007-04-20 21:23

Subject: git via rsync
Message-ID: <Pine.LNX.4.64.0704202218480.7764@beast.quantumfyre.co.uk>
URL: https://gitlist.dev/e/Pine.LNX.4.64.0704202218480.7764%40beast.quantumfyre.co.uk

```
Is rsync still a supported git transport (I know that there is still 
code for it, but does anyone care for it)?  Does anyone use it?

http has caused a couple of queries recently, but I haven't noticed 
anything about rsync.  Does that mean that it "just works", or is it 
simply that no one uses it?

Just curious ...

-- 
Julian

  ---
Children are unpredictable.  You never know what inconsistency they're
going to catch you in next.
 		-- Franklin P. Jones

```

## Rogan Dawes, 2007-04-21 07:24

Subject: Re: git via rsync
Message-ID: <4629BC43.1060603@dawes.za.net>
URL: https://gitlist.dev/e/4629BC43.1060603%40dawes.za.net
In-Reply-To: <Pine.LNX.4.64.0704202218480.7764@beast.quantumfyre.co.uk>

```
Julian Phillips wrote:
> Is rsync still a supported git transport (I know that there is still 
> code for it, but does anyone care for it)?  Does anyone use it?
> 
> http has caused a couple of queries recently, but I haven't noticed 
> anything about rsync.  Does that mean that it "just works", or is it 
> simply that no one uses it?
> 
> Just curious ...
> 

Rsync has significant problems that prevent it being used in serious 
situations.

Primarily, it is not atomic. So, if the other end is busy with an 
operation while you are rsyncing, you are likely to get a corrupted fetch.

I'm sure that there are others, but I don't remember them offhand.

Rogan

```
