From: Karthik Nayak <karthik.188@gmail.com>
To: git@vger.kernel.org
Cc: Karthik Nayak <karthik.188@gmail.com>,
ps@pks.im, gitster@pobox.com, jltobler@gmail.com,
kristofferhaugsbakk@fastmail.com,
Phillip Wood <phillip.wood@dunelm.org.uk>
Subject: [PATCH v3 2/3] receive-pack: move message generation to separate function
Date: Mon, 24 Aug 2026 12:21:00 +0200 [thread overview]
Message-ID: <20260824-758-introduce-hook-v3-2-499526f0a062@gmail.com> (raw)
In-Reply-To: <20260824-758-introduce-hook-v3-0-499526f0a062@gmail.com>
Post the reference transaction, both `report()` and `report_v2()`
generate the message to be sent to the client. In v2, we also add
reports for each reference if available. Since they share common code,
move them to a common function. This will also help the following
commit, where we will need to regenerate the message during hook
failure.
Signed-off-by: Karthik Nayak <karthik.188@gmail.com>
---
builtin/receive-pack.c | 84 ++++++++++++++++++++++++++------------------------
1 file changed, 44 insertions(+), 40 deletions(-)
diff --git a/builtin/receive-pack.c b/builtin/receive-pack.c
index 86933d8d7e..70a686c142 100644
--- a/builtin/receive-pack.c
+++ b/builtin/receive-pack.c
@@ -2530,67 +2530,71 @@ static void update_shallow_info(struct command *commands,
free(ref_status);
}
-static void report(struct command *commands, const char *unpack_status)
+/*
+ * Generate the response to be sent to the client invoking 'git-receive-pack(1)'.
+ * For v2 protocol, set `add_reports` to true, which will also add additional
+ * report per reference update.
+ */
+static void generate_response(struct strbuf *buf, struct command *commands,
+ const char *unpack_status, bool add_reports)
{
struct command *cmd;
- struct strbuf buf = STRBUF_INIT;
- packet_buf_write(&buf, "unpack %s\n",
+ packet_buf_write(buf, "unpack %s\n",
unpack_status ? unpack_status : "ok");
- for (cmd = commands; cmd; cmd = cmd->next) {
- if (!cmd->error_string)
- packet_buf_write(&buf, "ok %s\n",
- cmd->ref_name);
- else
- packet_buf_write(&buf, "ng %s %s\n",
- cmd->ref_name, cmd->error_string);
- }
- packet_buf_flush(&buf);
-
- if (use_sideband)
- send_sideband(1, 1, buf.buf, buf.len, use_sideband);
- else
- write_or_die(1, buf.buf, buf.len);
- strbuf_release(&buf);
-}
-
-static void report_v2(struct command *commands, const char *unpack_status)
-{
- struct command *cmd;
- struct strbuf buf = STRBUF_INIT;
- struct ref_push_report *report;
- packet_buf_write(&buf, "unpack %s\n",
- unpack_status ? unpack_status : "ok");
for (cmd = commands; cmd; cmd = cmd->next) {
+ struct ref_push_report *report;
int count = 0;
- if (cmd->error_string) {
- packet_buf_write(&buf, "ng %s %s\n",
- cmd->ref_name,
- cmd->error_string);
+ if (cmd->error_string)
+ packet_buf_write(buf, "ng %s %s\n",
+ cmd->ref_name, cmd->error_string);
+ else
+ packet_buf_write(buf, "ok %s\n", cmd->ref_name);
+
+ if (!add_reports || cmd->error_string)
continue;
- }
- packet_buf_write(&buf, "ok %s\n",
- cmd->ref_name);
+
for (report = cmd->report; report; report = report->next) {
if (count++ > 0)
- packet_buf_write(&buf, "ok %s\n",
+ packet_buf_write(buf, "ok %s\n",
cmd->ref_name);
if (report->ref_name)
- packet_buf_write(&buf, "option refname %s\n",
+ packet_buf_write(buf, "option refname %s\n",
report->ref_name);
if (report->old_oid)
- packet_buf_write(&buf, "option old-oid %s\n",
+ packet_buf_write(buf, "option old-oid %s\n",
oid_to_hex(report->old_oid));
if (report->new_oid)
- packet_buf_write(&buf, "option new-oid %s\n",
+ packet_buf_write(buf, "option new-oid %s\n",
oid_to_hex(report->new_oid));
if (report->forced_update)
- packet_buf_write(&buf, "option forced-update\n");
+ packet_buf_write(buf, "option forced-update\n");
}
}
- packet_buf_flush(&buf);
+
+ packet_buf_flush(buf);
+}
+
+static void report(struct command *commands, const char *unpack_status)
+{
+ struct strbuf buf = STRBUF_INIT;
+
+ generate_response(&buf, commands, unpack_status, false);
+
+ if (use_sideband)
+ send_sideband(1, 1, buf.buf, buf.len, use_sideband);
+ else
+ write_or_die(1, buf.buf, buf.len);
+ strbuf_release(&buf);
+}
+
+static void report_v2(struct command *commands, const char *unpack_status)
+{
+ struct strbuf buf = STRBUF_INIT;
+
+ generate_response(&buf, commands, unpack_status, true);
if (use_sideband)
send_sideband(1, 1, buf.buf, buf.len, use_sideband);
--
2.55.GIT
next prev parent reply other threads:[~2026-08-24 10:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 7:55 [PATCH] hook: introduce the report hook for git-receive-pack(1) Karthik Nayak
2026-08-18 20:54 ` Junio C Hamano
2026-08-19 7:03 ` Kristoffer Haugsbakk
2026-08-19 12:11 ` Karthik Nayak
2026-08-19 14:47 ` Kristoffer Haugsbakk
2026-08-19 7:39 ` Patrick Steinhardt
2026-08-19 13:13 ` Karthik Nayak
2026-08-19 13:20 ` Patrick Steinhardt
2026-08-19 13:24 ` Karthik Nayak
2026-08-20 9:50 ` Phillip Wood
2026-08-20 15:43 ` Junio C Hamano
2026-08-21 12:51 ` Karthik Nayak
2026-08-21 13:34 ` [PATCH v2] " Karthik Nayak
2026-08-21 13:49 ` Patrick Steinhardt
2026-08-21 16:08 ` Karthik Nayak
2026-08-24 5:32 ` Patrick Steinhardt
2026-08-24 8:14 ` Karthik Nayak
2026-08-21 16:55 ` Junio C Hamano
2026-08-24 10:20 ` [PATCH v3 0/3] " Karthik Nayak
2026-08-24 10:20 ` [PATCH v3 1/3] doc: add proc-receive hook info in 'git-receive-pack.adoc' Karthik Nayak
2026-08-24 10:21 ` Karthik Nayak [this message]
2026-08-24 10:21 ` [PATCH v3 3/3] hook: introduce the report hook for git-receive-pack(1) Karthik Nayak
2026-08-24 15:35 ` [PATCH v3 0/3] " Junio C Hamano
2026-08-24 15:57 ` Junio C Hamano
2026-08-24 17:00 ` Patrick Steinhardt
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=20260824-758-introduce-hook-v3-2-499526f0a062@gmail.com \
--to=karthik.188@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jltobler@gmail.com \
--cc=kristofferhaugsbakk@fastmail.com \
--cc=phillip.wood@dunelm.org.uk \
--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