From: Patrick Steinhardt <ps@pks.im>
To: git@vger.kernel.org
Cc: Taylor Blau <me@ttaylorr.com>
Subject: [PATCH v2 0/2] repack: add config to skip updating server info
Date: Mon, 14 Mar 2022 08:42:42 +0100 [thread overview]
Message-ID: <cover.1647243508.git.ps@pks.im> (raw)
In-Reply-To: <659d5528df56f6b9aece6b1f3c4e2e5a4ae04e1e.1646996936.git.ps@pks.im>
[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]
Hi,
this is the second version of my patch series which adds a new config to
allow users and admins to permanently skip updating server info required
for the dumb HTTP protocol in git-repack(1).
The following things changed in comparison to v1:
- I've split out a preparatory patch which refactors the logic to
avoid double-negation of the `no_update_server_info` field.
- I've updated documentation to be more explicit with regards to the
default of the new config and to mention that the `-n` flag
overrides it.
- I've refactored tests to be less verbose.
Thanks for your feedback, Taylor!
Patrick
Patrick Steinhardt (2):
repack: refactor to avoid double-negation of update-server-info
repack: add config to skip updating server info
Documentation/config/repack.txt | 5 ++++
builtin/repack.c | 12 +++++---
t/t7700-repack.sh | 50 +++++++++++++++++++++++++++++++++
3 files changed, 63 insertions(+), 4 deletions(-)
--
2.35.1
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-03-14 7:42 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 ` Patrick Steinhardt [this message]
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
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=cover.1647243508.git.ps@pks.im \
--to=ps@pks.im \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.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.
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).