From: Junio C Hamano <gitster@pobox•com>
To: Jeff King <peff@peff•net>
Cc: Jonathan Tan <jonathantanmy@google•com>, git@vger•kernel.org
Subject: Re: [WIP v2 2/2] pack-objects: support --blob-max-bytes
Date: Sun, 04 Jun 2017 08:48:38 +0900 [thread overview]
Message-ID: <xmqqinkcws2x.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20170602222640.u6vni5tdpjp3sayt@sigill.intra.peff.net> (Jeff King's message of "Fri, 2 Jun 2017 18:26:40 -0400")
Jeff King <peff@peff•net> writes:
> I do also wonder if the two features would need to be separated for a
> GVFS-style solution. If you're not just avoiding large blobs but trying
> to get a narrow clone, you don't want the .git files from the
> uninteresting parts of the tree. You want to get no blobs at all, and
> then fault them in as they become relevant due to user action.
Thanks; I didn't think of this one while reviewing the overall design,
but I agree that this is something important to think about.
next prev parent reply other threads:[~2017-06-03 23:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 0:14 [WIP 0/2] Modifying pack-objects to support --blob-size-limit Jonathan Tan
2017-06-02 0:14 ` [WIP 1/2] pack-objects: rename want_.* to ignore_.* Jonathan Tan
2017-06-02 3:45 ` Junio C Hamano
2017-06-02 0:14 ` [WIP 2/2] pack-objects: support --blob-size-limit Jonathan Tan
2017-06-02 4:48 ` Junio C Hamano
2017-06-02 19:38 ` [WIP v2 0/2] Modifying pack objects to support --blob-max-bytes Jonathan Tan
2017-06-02 19:38 ` [WIP v2 1/2] pack-objects: rename want_.* to ignore_.* Jonathan Tan
2017-06-02 19:38 ` [WIP v2 2/2] pack-objects: support --blob-max-bytes Jonathan Tan
2017-06-02 22:26 ` Jeff King
2017-06-02 23:25 ` Jonathan Nieder
2017-06-07 9:44 ` Jeff King
2017-06-03 23:48 ` Junio C Hamano [this message]
2017-06-15 20:28 ` Jeff Hostetler
2017-06-15 21:03 ` Jonathan Tan
2017-06-02 22:16 ` [WIP v2 0/2] Modifying pack objects to " Jeff King
2017-06-05 17:35 ` Jonathan Tan
2017-06-07 9:46 ` Jeff King
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=xmqqinkcws2x.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=jonathantanmy@google$(echo .)com \
--cc=peff@peff$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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