From: Junio C Hamano <gitster@pobox.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: git@vger.kernel.org, Taylor Blau <me@ttaylorr.com>
Subject: Re: [PATCH v2 2/2] repack: add config to skip updating server info
Date: Mon, 14 Mar 2022 22:26:47 +0000 [thread overview]
Message-ID: <xmqq5yognpaw.fsf@gitster.g> (raw)
In-Reply-To: <f8639116d2d384a6d285c75830c52d8a8230ae6b.1647243509.git.ps@pks.im> (Patrick Steinhardt's message of "Mon, 14 Mar 2022 08:42:51 +0100")
Patrick Steinhardt <ps@pks.im> writes:
> By default, git-repack(1) will update server info that is required by
> the dumb HTTP transport. This can be skipped by passing the `-n` flag,
> but what we're noticably missing is a config option to permanently
> disable updating this information.
>
> Add a new option "repack.updateServerInfo" which can be used to disable
> the logic. Most hosting providers have turned off the dumb HTTP protocol
> anyway, and on the client-side it woudln't typically be useful either.
> Giving a persistent way to disable this feature thus makes quite some
> sense to avoid wasting compute cycles and storage.
Makes sense. Perhaps we can leave a NEEDSWORK comment somewhere to
flip the default to false in two years or so.
Will queue.
Thanks.
prev parent reply other threads:[~2022-03-14 22:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 11:09 [PATCH] repack: add config to skip updating server info Patrick Steinhardt
2022-03-11 16:20 ` Taylor Blau
2022-03-14 7:19 ` Patrick Steinhardt
2022-03-14 7:42 ` [PATCH v2 0/2] " Patrick Steinhardt
2022-03-14 7:42 ` [PATCH v2 1/2] repack: refactor to avoid double-negation of update-server-info Patrick Steinhardt
2022-03-14 7:42 ` [PATCH v2 2/2] repack: add config to skip updating server info Patrick Steinhardt
2022-03-14 22:26 ` Junio C Hamano [this message]
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=xmqq5yognpaw.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.com \
--cc=ps@pks.im \
/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).