From: Junio C Hamano <gitster@pobox.com>
To: Li Chen <me@linux.beauty>
Cc: "phillipwood" <phillip.wood@dunelm.org.uk>, "git" <git@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] trailer: append trailers in-process and drop the fork to `interpret-trailers`
Date: Tue, 10 Jun 2025 17:09:19 -0700 [thread overview]
Message-ID: <xmqq8qlzkukw.fsf@gitster.g> (raw)
In-Reply-To: <20250610123459.278582-2-me@linux.beauty> (Li Chen's message of "Tue, 10 Jun 2025 20:34:58 +0800")
Li Chen <me@linux.beauty> writes:
> * `amend_strbuf_with_trailers()`
> – parses the existing message,
> – merges trailers from the command line and config,
> – formats the final trailer block, and
> – rewrites the supplied `struct strbuf`
> without ever leaving the current process.
If such a helper function exists, shouldn't "interpret-trailers" be
able to lose quite a lot of lines, at least nearly as many as the
new lines introduced to this new function, by making it call this
function as well? And that would ensure that the internal call can
safely replace the external call and produce exactly the same
output? If so, that can be a pure refactoring patch that can become
a commit on its own, I presume?
> * `amend_file_with_trailers()` becomes a thin wrapper that reads a file
> into a `strbuf`, calls the new helper, and writes the result back.
> * `builtin/rebase.c` now calls `amend_file_with_trailers()` instead of
> executing `interpret-trailers`.
And then these two changes can become a separate patch on top?
> -int amend_file_with_trailers(const char *path, const struct strvec *trailer_args)
This lone "removed line" can be avoided if the patch did not touch
this line ...
> +static size_t first_comment_pos(const struct strbuf *buf)
> {
> - struct child_process run_trailer = CHILD_PROCESS_INIT;
> -
> - run_trailer.git_cmd = 1;
> - strvec_pushl(&run_trailer.args, "interpret-trailers",
> - "--in-place", "--no-divider",
> - path, NULL);
> - strvec_pushv(&run_trailer.args, trailer_args->v);
> - return run_command(&run_trailer);
> + const char *p = buf->buf;
> + const char *end = buf->buf + buf->len;
> +
> + while (p < end) {
> + const char *line = p;
> + const char *nl = memchr(p, '\n', end - p);
> + size_t len = nl ? (size_t)(nl - p) : (size_t)(end - p);
> +
> + /* skip leading whitespace */
> + size_t i = 0;
> + while (i < len && isspace((unsigned char)line[i]))
> + i++;
> +
> + if (i < len && line[i] == '#')
> + return (size_t)(line - buf->buf); /* comment starts here */
> +
> + if (!nl) /* last line without newline */
> + break;
> + p = nl + 1;
> + }
> + return buf->len; /* no comment line found */
> +}
> +
> +int amend_strbuf_with_trailers(struct strbuf *buf,
> + const struct strvec *trailer_args)
... like this?
next prev parent reply other threads:[~2025-06-11 0:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 12:34 [PATCH v2 0/2] rebase: support --trailer Li Chen
2025-06-10 12:34 ` [PATCH v2 1/2] trailer: append trailers in-process and drop the fork to `interpret-trailers` Li Chen
2025-06-11 0:09 ` Junio C Hamano [this message]
2025-06-11 9:15 ` phillip.wood123
2025-06-11 15:34 ` Junio C Hamano
2025-06-12 5:40 ` Li Chen
2025-06-10 12:34 ` [PATCH v2 2/2] rebase: support --trailer Li Chen
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=xmqq8qlzkukw.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=me@linux.beauty \
--cc=phillip.wood@dunelm.org.uk \
/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