git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Pitre <nico@fluxnic.net>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: Jason Merrill <jason@redhat.com>,
	git@vger.kernel.org, Hin-Tak Leung <hintak.leung@gmail.com>
Subject: Re: git clone sending unneeded objects
Date: Fri, 25 Sep 2009 15:53:09 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.00.0909251551290.4997@xanadu.home> (raw)
In-Reply-To: <vpqvdj6izt6.fsf@bauges.imag.fr>

On Fri, 25 Sep 2009, Matthieu Moy wrote:

> Jason Merrill <jason@redhat.com> writes:
> 
> > On 08/09/2009 03:43 AM, Andreas Schwab wrote:
> >> Nicolas Pitre<nico@cam.org>  writes:
> >>
> >>> If you do a clone using the git:// protocol and the server sends you
> >>> only the ref for the trunk branch,
> >>
> >> A clone will fetch all branches from refs/heads/*.
> >>
> >>> then it should send you only objects reachable from that branch.
> >>
> >> Apparantly this does not work.  I'd guess the extra objects are needed
> >> due to the delta compression.
> >
> > I just tried doing a clone of the GCC repository, then git gc
> > --prune=now, and another clone specifying --reference to the first,
> > and it wanted to download all the unreachable objects again.  So it
> > doesn't seem to be a compression issue.
> >
> > This is with git 1.6.4 on both ends.
> 
> Which protocol did you use?
> 
> If you use git:// or ssh://, it's normally a security feature that Git
> sends you only reachable objects. If it doesn't, it's a serious bug.

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.


Nicolas

  parent reply	other threads:[~2009-09-25 19:53 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 [this message]
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

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=alpine.LFD.2.00.0909251551290.4997@xanadu.home \
    --to=nico@fluxnic.net \
    --cc=Matthieu.Moy@grenoble-inp.fr \
    --cc=git@vger.kernel.org \
    --cc=hintak.leung@gmail.com \
    --cc=jason@redhat.com \
    /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).