All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nigel Cunningham <ncunningham@cyclades.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Does a git pull have to be so big?
Date: Fri, 13 Jan 2006 09:11:46 +1000	[thread overview]
Message-ID: <200601130911.46761.ncunningham@cyclades.com> (raw)
In-Reply-To: <20060112225434.GA27678@havoc.gtf.org>

Hi.

On Friday 13 January 2006 08:54, Jeff Garzik wrote:
> 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.

Thanks for the reply. Can I avoid using pack files with Linus' tree? If so, 
how?

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

Ok. I can cope with that. Redownloading the whole history however, I'd like to 
stop.

Regards,

Nigel

      reply	other threads:[~2006-01-12 23:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-12 22:45 Does a git pull have to be so big? Nigel Cunningham
2006-01-12 22:48 ` Brian Gerst
2006-01-12 23:12   ` Nigel Cunningham
2006-01-12 23:44     ` Brian Gerst
2006-01-13  0:00       ` Nigel Cunningham
2006-01-12 22:54 ` Jeff Garzik
2006-01-12 23:11   ` Nigel Cunningham [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200601130911.46761.ncunningham@cyclades.com \
    --to=ncunningham@cyclades.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.