git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hin-Tak Leung <hintak.leung@gmail.com>
To: Jason Merrill <jason@redhat.com>
Cc: Nicolas Pitre <nico@fluxnic.net>,
	Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>,
	git@vger.kernel.org
Subject: Re: git clone sending unneeded objects
Date: Sat, 26 Sep 2009 01:43:57 +0100	[thread overview]
Message-ID: <3ace41890909251743v7a51027agb039514dd0636058@mail.gmail.com> (raw)
In-Reply-To: <4ABD25FE.2040902@redhat.com>

On Fri, Sep 25, 2009 at 9:20 PM, Jason Merrill <jason@redhat.com> wrote:
> On 09/25/2009 03:53 PM, Nicolas Pitre wrote:
>>
>> I did reproduce the issue with git:// back when this discussion started.
>> I also asked for more information about the remote which didn't come
>> forth.
>
> Looking back, I only see you asking about the git version on the server,
> which is 1.6.4.

Hmm, I was under the impression from the previous thread that the
server is a bit older and/or have more backward compatible settings to
cater for older git clients?

>
> So again:
>
> git clone git://gcc.gnu.org/git/gcc.git
>  (1399509 objects, ~600MB .git dir)
> git gc --prune=now (988906 objects, ~450MB .git dir)
>
> ...then
>
> git clone git://gcc.gnu.org/git/gcc.git --reference $firstclone
>  (573401 objects, ~550MB .git dir)
> git fsck (clean)
> git gc --prune=now (5 objects, ~7MB .git dir)
>
> What's going on here?

FWIW, I still have my clone (git://) and do my periodic 'git fetch'
and 'git gc prune=now' (learned my lessons!) and it is currently .git
dir is about 350MB. (from previous discussion the optimal at the time
was about 300MB, so it has grown a bit in the last couple of months).

And thanks everybody for all the discussion and advice. git is a great
tool. (and I have essentially stopped using svn, prefering git-svn!).

      parent reply	other threads:[~2009-09-26  0:44 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-08  1:11 git gc expanding packed data? Andreas Schwab
2009-08-08 13:05 ` Hin-Tak Leung
2009-08-08 13:25   ` Andreas Schwab
2009-08-09  2:56 ` Nicolas Pitre
2009-08-09  7:43   ` Andreas Schwab
2009-09-25 18:05     ` git clone sending unneeded objects (was : git gc expanding packed data?) Jason Merrill
2009-09-25 19:34       ` git clone sending unneeded objects Matthieu Moy
2009-09-25 19:43         ` Jason Merrill
2009-09-25 19:53         ` Nicolas Pitre
2009-09-25 20:20           ` Jason Merrill
2009-09-25 20:47             ` Nicolas Pitre
2009-09-25 23:17               ` Jason Merrill
2009-09-26  0:49                 ` Nicolas Pitre
2009-09-26  3:54                   ` [PATCH] make 'git clone' ask the remote only for objects it cares about Nicolas Pitre
2009-09-26  7:21                     ` Andreas Schwab
2009-09-26 19:50                     ` Shawn O. Pearce
2009-09-27  0:26                       ` Nicolas Pitre
2009-09-26  4:44                 ` git clone sending unneeded objects Jason Merrill
2009-09-26 13:33                   ` Jason Merrill
2009-09-27  2:26                     ` Nicolas Pitre
2009-09-27  1:27                   ` Nicolas Pitre
2009-09-27  2:04                     ` Shawn O. Pearce
2009-09-27  2:31                       ` Nicolas Pitre
2009-09-27  4:35                       ` Jason Merrill
2009-09-28  4:18                         ` Nicolas Pitre
2009-09-26  0:43             ` Hin-Tak Leung [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=3ace41890909251743v7a51027agb039514dd0636058@mail.gmail.com \
    --to=hintak.leung@gmail.com \
    --cc=Matthieu.Moy@grenoble-inp.fr \
    --cc=git@vger.kernel.org \
    --cc=jason@redhat.com \
    --cc=nico@fluxnic.net \
    /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;
as well as URLs for NNTP newsgroup(s).