From: "mark at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: overseers@gcc.gnu.org
Subject: [Bug web/114223] Utilize filtering for git://gcc.gnu.org/git/gcc.git
Date: Sun, 03 Mar 2024 21:01:35 +0000 [thread overview]
Message-ID: <bug-114223-5127-vy8RW7ubqF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114223-5127@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114223
Mark Wielaard <mark at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mark at gcc dot gnu.org
--- Comment #1 from Mark Wielaard <mark at gcc dot gnu.org> ---
I believe this is enabled by setting the following settings described at
https://git-scm.com/docs/git-config#Documentation/git-config.txt-uploadpackallowFilter
uploadpack.allowFilter
If this option is set, upload-pack will support partial clone and partial
fetch object filtering.
uploadpackfilter.allow
Provides a default value for unspecified object filters (see: the below
configuration variable). If set to true, this will also enable all filters
which get added in the future. Defaults to true.
uploadpackfilter.<filter>.allow
Explicitly allow or ban the object filter corresponding to <filter>, where
<filter> may be one of: blob:none, blob:limit, object:type, tree, sparse:oid,
or combine. If using combined filters, both combine and all of the nested
filter kinds must be allowed. Defaults to uploadpackfilter.allow.
uploadpackfilter.tree.maxDepth
Only allow --filter=tree:<n> when <n> is no more than the value of
uploadpackfilter.tree.maxDepth. If set, this also implies
uploadpackfilter.tree.allow=true, unless this configuration variable had
already been set. Has no effect if unset.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2024-03-03 21:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-114223-5127@http.gcc.gnu.org/bugzilla/>
2024-03-03 20:20 ` pinskia at gcc dot gnu.org
2024-03-03 21:01 ` mark at gcc dot gnu.org [this message]
2024-03-04 2:07 ` fche at redhat dot com
2024-03-04 10:30 ` redi at gcc dot gnu.org
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=bug-114223-5127-vy8RW7ubqF@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=overseers@gcc.gnu.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).