From: Patrick Steinhardt <ps@pks.im>
To: git@vger.kernel.org
Cc: Christian Couder <chriscool@tuxfamily.org>
Subject: [PATCH 0/2] refs: stylistic improvements to ref migration optimization
Date: Mon, 25 Nov 2024 08:34:41 +0100 [thread overview]
Message-ID: <20241125-pks-refs-migration-optimization-followup-v1-0-0e1b4a2af384@pks.im> (raw)
Hi,
this small patch series addresses some stylistic nits surfaced in the
review of ps/ref-backend-migration-optim. v3 of that series and the
merge to `next` have crossed, so I'm resending the changes from v3 on
top of what we have in `next`.
This version is built on top of 6ea2d9d271 (Sync with Git 2.47.1,
2024-11-25) with ps/ref-backend-migration-optim at d94ac23d3b
(reftable/block: optimize allocations by using scratch buffer,
2024-11-20) merged into it.
Thanks!
Patrick
---
Patrick Steinhardt (2):
refs: adapt `initial_transaction` flag to be unsigned
reftable: rename scratch buffer
refs.c | 2 +-
refs.h | 2 +-
reftable/block.c | 10 +++++-----
reftable/block.h | 3 ++-
reftable/writer.c | 22 +++++++++++-----------
reftable/writer.h | 3 ++-
6 files changed, 22 insertions(+), 20 deletions(-)
---
base-commit: a468246cedfb3b54b03609be75d9e13f0be1cc29
change-id: 20241125-pks-refs-migration-optimization-followup-d766e86b8925
next reply other threads:[~2024-11-25 7:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-25 7:34 Patrick Steinhardt [this message]
2024-11-25 7:34 ` [PATCH 1/2] refs: adapt `initial_transaction` flag to be unsigned Patrick Steinhardt
2024-11-26 8:22 ` Junio C Hamano
2024-11-25 7:34 ` [PATCH 2/2] reftable: rename scratch buffer Patrick Steinhardt
2024-11-25 9:35 ` [PATCH 0/2] refs: stylistic improvements to ref migration optimization Christian Couder
2024-11-25 23:39 ` 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=20241125-pks-refs-migration-optimization-followup-v1-0-0e1b4a2af384@pks.im \
--to=ps@pks.im \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.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 NNTP newsgroup(s).