From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: sverre@rabbelier.nl
Cc: "Petr Baudis" <pasky@suse.cz>, "Jeff King" <peff@peff.net>,
"Nguy?n Thái Ng?c Duy" <pclouds@gmail.com>,
git@vger.kernel.org
Subject: Re: sparse fetch, was Re: [PATCH 08/12] git-clone: support --path to do sparse clone
Date: Fri, 25 Jul 2008 02:12:31 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.1.00.0807250210090.4140@eeepc-johanness> (raw)
In-Reply-To: <bd6139dc0807241201v50cd5ef2m58ee7efc05119e20@mail.gmail.com>
Hi,
On Thu, 24 Jul 2008, Sverre Rabbelier wrote:
> On Thu, Jul 24, 2008 at 8:53 PM, Petr Baudis <pasky@suse.cz> wrote:
> > I don't follow how these two issues arise, if the server will do the
> > pruning for you. It will just skip entering some tree objects when
> > doing object traversal; why opening the git protocol or faking
> > commits? This would be a simple extra capability in the protocol.
>
> Wouldn't that be as simple as passing a pathspec to git-rev-list? Not a
> lot of overhead there I reckon.
So the server would _not_ have to deflate the objects to inspect them? I
thought you knew more about Git's object database.
> > One question is what to do with delta chains including unwanted
> > objects, but I think that given the objects' associativity for delta
> > chains, this shouldn't be huge practical issues and it could be
> > affordable in principle to include even unwanted objects.
>
> Just keep them?
You'd still have to inspect the objects, which is way more work than the
current code has to do. Remember: in the optimal case, upload-pack does
not more than just serve the existing deltas/base objects.
Ciao,
Dscho
next prev parent reply other threads:[~2008-07-25 0:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-23 14:57 [PATCH 10/12] git-checkout: support --full and --path to manipulate sparse checkout Nguyễn Thái Ngọc Duy
2008-07-23 14:57 ` [PATCH 08/12] git-clone: support --path to do sparse clone Nguyễn Thái Ngọc Duy
2008-07-23 14:56 ` [PATCH 03/12] Introduce sparse prefix Nguyễn Thái Ngọc Duy
2008-07-23 14:55 ` [PATCH 02/12] git-grep: support --no-external-grep Nguyễn Thái Ngọc Duy
2008-07-23 19:01 ` Petr Baudis
2008-07-23 19:05 ` Petr Baudis
2008-07-24 20:26 ` Alex Riesen
2008-07-24 23:16 ` Nguyen Thai Ngoc Duy
2008-07-24 17:19 ` [PATCH 08/12] git-clone: support --path to do sparse clone Jeff King
2008-07-24 17:41 ` sparse fetch, was " Johannes Schindelin
2008-07-24 18:28 ` Jeff King
2008-07-25 0:09 ` Johannes Schindelin
2008-07-25 0:46 ` James Pickens
2008-07-25 0:49 ` sparse fetch, was Re: [PATCH 08/12] git-clone: support --path?to " Jeff King
2008-07-25 8:47 ` sparse fetch, was Re: [PATCH 08/12] git-clone: support --path to " Junio C Hamano
2008-07-25 8:54 ` Sverre Rabbelier
2008-07-24 18:44 ` Nguyen Thai Ngoc Duy
2008-07-24 18:53 ` Petr Baudis
2008-07-24 19:01 ` Sverre Rabbelier
2008-07-25 0:12 ` Johannes Schindelin [this message]
2008-07-25 0:42 ` Petr Baudis
2008-07-25 8:14 ` Sverre Rabbelier
2008-07-24 18:47 ` Nguyen Thai Ngoc Duy
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.DEB.1.00.0807250210090.4140@eeepc-johanness \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=pasky@suse.cz \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
--cc=sverre@rabbelier.nl \
/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