From: Jonathan Tan <jonathantanmy@google.com>
To: Stefan Beller <sbeller@google.com>
Cc: Ciro Santilli <ciro.santilli@gmail.com>,
Matthew DeVore <matvore@google.com>, git <git@vger.kernel.org>
Subject: Re: Is it possible to git clone --filter= without any objects?
Date: Tue, 11 Sep 2018 10:19:03 -0700 [thread overview]
Message-ID: <CAGf8dgKLz14ijnXwV0Y=M48Rij-scA19E_uXk3pBc0T02oE_0Q@mail.gmail.com> (raw)
In-Reply-To: <CAGZ79kYK7ish4_DaZN2bCfZz7LNAjxogQH1k6T=hFcxxkXzJQw@mail.gmail.com>
On Tue, Sep 11, 2018 at 10:15 AM, Stefan Beller <sbeller@google.com> wrote:
> You might be pleased to hear about a series floating on the mailing list,
> that started at
> https://public-inbox.org/git/cover.1533854545.git.matvore@google.com/
> and promised to filter trees away, and its latest version can be found at
> https://public-inbox.org/git/cover.1536081438.git.matvore@google.com/
I mentioned this in an email to the original poster in which I forgot
to also CC the mailing list:
By "without any objects" in your email subject, do you mean "without
blob and tree objects"? If yes, there is some code in the
md/filter-trees branch that can do that with a "--filter=tree:0"
option. As far as I know, it is not yet in any released version of
Git, but hopefully will be in the next one (the "What's Cooking" [1]
email mentions that it will be merged to the "next" branch, which is
one of the steps before it is released).
[1] https://public-inbox.org/git/xmqqmusw6gbo.fsf@gitster-ct.c.googlers.com/
next prev parent reply other threads:[~2018-09-11 17:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 7:29 Is it possible to git clone --filter= without any objects? Ciro Santilli
2018-09-11 17:15 ` Stefan Beller
2018-09-11 17:19 ` Jonathan Tan [this message]
2018-09-11 17:46 ` Junio C Hamano
2018-09-11 18:29 ` Ciro Santilli
2018-09-12 1:12 ` Matthew DeVore
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAGf8dgKLz14ijnXwV0Y=M48Rij-scA19E_uXk3pBc0T02oE_0Q@mail.gmail.com' \
--to=jonathantanmy@google.com \
--cc=ciro.santilli@gmail.com \
--cc=git@vger.kernel.org \
--cc=matvore@google.com \
--cc=sbeller@google.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).