From: Nigel Cunningham <ncunningham@cyclades.com>
To: Brian Gerst <bgerst@didntduck.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Does a git pull have to be so big?
Date: Fri, 13 Jan 2006 10:00:49 +1000 [thread overview]
Message-ID: <200601131000.49553.ncunningham@cyclades.com> (raw)
In-Reply-To: <43C6E9CC.60509@didntduck.org>
Hi.
On Friday 13 January 2006 09:44, Brian Gerst wrote:
> Nigel Cunningham wrote:
> > Hi.
> >
> > On Friday 13 January 2006 08:48, Brian Gerst wrote:
> >> Nigel Cunningham wrote:
> >>> Hi.
> >>>
> >>> 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?
> >>>
> >>> I'm using cogito .16-2 (ubuntu) and git 1.0.6.
> >>>
> >>> Regards,
> >>>
> >>> Nigel
> >>>
> >>> #cg-fetch
> >>> Fetching head...
> >>> Fetching objects...
> >>> progress: 114 objects, 256992 bytes
> >>> Getting alternates list for
> >>> http://www.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git/
> >>> progress: 376 objects, 1413225 bytes
> >>> Getting pack list for
> >>> http://www.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git/
> >>> progress: 453 objects, 1924312 bytes
> >>> Getting index for pack 221c50e73e5ab65afededc14f1df0541b59ebdd5
> >>> Getting pack 221c50e73e5ab65afededc14f1df0541b59ebdd5
> >>> which contains 62727f8969438d99c3c34415d16611cf86f16140
> >>>
> >>> (Still going)
> >>> -
> >>> 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/
> >>
> >> Use git://git.kernel.org/... instead of http.
> >>
> >> --
> >> Brian Gerst
> >
> > Ok. I'll give it a try - is it related to the packed files thing Jeff
> > spoke of?
> >
> > Regards,
> >
> > Nigel
>
> Yes. If the objects are packed then the only way to get the objects by
> http are to download the whole pack.
Ah. Well, I've followed the advice and switched to git://. Thanks again!
Nigel
next prev parent reply other threads:[~2006-01-13 0:00 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 [this message]
2006-01-12 22:54 ` Jeff Garzik
2006-01-12 23:11 ` Nigel Cunningham
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=200601131000.49553.ncunningham@cyclades.com \
--to=ncunningham@cyclades.com \
--cc=bgerst@didntduck.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox