Date: Thu, 12 Jan 2006 17:54:34 -0500
From: Jeff Garzik <jgarzik@pobox.com>
To: Nigel Cunningham <ncunningham@cyclades.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Does a git pull have to be so big?
Message-ID: <20060112225434.GA27678@havoc.gtf.org>
References: <200601130845.29797.ncunningham@cyclades.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200601130845.29797.ncunningham@cyclades.com>
User-Agent: Mutt/1.4.1i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 952
Lines: 25

On Fri, Jan 13, 2006 at 08:45:29AM +1000, Nigel Cunningham wrote:
> I try to do pulls reasonably often, but they always seem to be huge downloads 
> - I'm sure they're orders of magnitude bigger than a simple patch would be. 
> This leads me to ask, do they have to be so big? I'm on 256/64 ADSL at home, 
> did a pull yesterday at work iirc, and yet the pull this morning has taken at 
> least half an hour. Am I perhaps doing something wrong?

Two answers here:

1) Every so often, you download the entire kernel history all over
again, if you are using pack files, since most repositories are repacked
occasionally.

2) Every change sends the full updated (albeit compressed) file,
not a patch.

	Jeff


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/