Re: Cloning from kernel.org, then switching to another repo

From: Jeff King <peff@peff.net>
Date: Nov 13, 2007, 04:14 UTC
Message-ID: <20071113041422.GA9745@sigill.intra.peff.net>
In-Reply-To: <9e4733910711120928r6d9d08f0l22f3c6f0b2d80313@mail.gmail.com>

On Mon, Nov 12, 2007 at 12:28:28PM -0500, Jon Smirl wrote:

Show 10 quoted lines

> Actually, fetching from kernel.org first and then switching the origin
> isn't helping. The host is http only since I can't get access to the
> git network port. When I pushed up my local repo it ends up in one big
> pack.
> 
> I do this:
> git clone kernel.org
> move the origin
> git pull
> -- it still pulls down the entire pack and takes an hour

Yep, the http fetch code doesn't understand about fetching parts of packs (there was some discussion about using partial HTTP transfers, but nobody seems to have cared enough to implement it).

> Will this fix it?
> at my remote host, first clone from kernel.org
> then push my local changes?

Yes, it should. The goal is to not put your changes and the upstream commits in the same pack. You could also push _just_ the upstream commits first, then in a different push, send your local changes. But when they get pushed together, they all end up in the same pack.

-Peff