From: "René Scharfe" <l.s.r@web.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: [PATCH] rebase: use strvec_pushf() for format-patch revisions
Date: Wed, 20 Dec 2023 09:04:35 +0100 [thread overview]
Message-ID: <47089803-c45b-4f33-b542-146c313f0902@web.de> (raw)
In-Reply-To: <xmqqmsu6ce0u.fsf@gitster.g>
Am 19.12.23 um 18:12 schrieb Junio C Hamano:
> René Scharfe <l.s.r@web.de> writes:
>
>> In run_am(), a strbuf is used to create a revision argument that is then
>> added to the argument list for git format-patch using strvec_push().
>> Use strvec_pushf() to add it directly instead, simplifying the code.
>>
>> Signed-off-by: René Scharfe <l.s.r@web.de>
>> ---
>
> Makes sense. Between the location of the original strbuf_addf()
> call and the new strvec_pushf() call, nobody mucks with *opts so
> this change won't affect the correctness. We no longer use the
> extra strbuf, and upon failing to open the rebased-patches file,
> we no longer leak the contents of it. Good.
Ha! I didn't even notice that leak on error. Perhaps the two release
calls at the end gave me the illusion of cleanliness? Or more likely
the opportunity to use strvec_pushf() grabbed my full attention (tunnel
vision).
>
>> @@ -615,34 +614,32 @@ static int run_am(struct rebase_options *opts)
>> return run_command(&am);
>> }
>>
>> - strbuf_addf(&revisions, "%s...%s",
>> - oid_to_hex(opts->root ?
>> - /* this is now equivalent to !opts->upstream */
>> - &opts->onto->object.oid :
>> - &opts->upstream->object.oid),
>> - oid_to_hex(&opts->orig_head->object.oid));
>> -
>> rebased_patches = xstrdup(git_path("rebased-patches"));
>> format_patch.out = open(rebased_patches,
>> O_WRONLY | O_CREAT | O_TRUNC, 0666);
>> if (format_patch.out < 0) {
>> status = error_errno(_("could not open '%s' for writing"),
>> rebased_patches);
>> free(rebased_patches);
>> strvec_clear(&am.args);
>> return status;
>> }
>>
>> format_patch.git_cmd = 1;
>> strvec_pushl(&format_patch.args, "format-patch", "-k", "--stdout",
>> "--full-index", "--cherry-pick", "--right-only",
>> "--default-prefix", "--no-renames",
>> "--no-cover-letter", "--pretty=mboxrd", "--topo-order",
>> "--no-base", NULL);
>> if (opts->git_format_patch_opt.len)
>> strvec_split(&format_patch.args,
>> opts->git_format_patch_opt.buf);
>> - strvec_push(&format_patch.args, revisions.buf);
>> + strvec_pushf(&format_patch.args, "%s...%s",
>> + oid_to_hex(opts->root ?
>> + /* this is now equivalent to !opts->upstream */
>> + &opts->onto->object.oid :
>> + &opts->upstream->object.oid),
>> + oid_to_hex(&opts->orig_head->object.oid));
>> if (opts->restrict_revision)
>> strvec_pushf(&format_patch.args, "^%s",
>> oid_to_hex(&opts->restrict_revision->object.oid));
>> @@ -665,10 +662,8 @@ static int run_am(struct rebase_options *opts)
>> "As a result, git cannot rebase them."),
>> opts->revisions);
>>
>> - strbuf_release(&revisions);
>> return status;
>> }
>> - strbuf_release(&revisions);
>>
>> am.in = open(rebased_patches, O_RDONLY);
>> if (am.in < 0) {
>> --
>> 2.43.0
next prev parent reply other threads:[~2023-12-20 8:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 7:42 [PATCH] rebase: use strvec_pushf() for format-patch revisions René Scharfe
2023-12-19 11:07 ` Phillip Wood
2023-12-19 12:25 ` Patrick Steinhardt
2023-12-19 17:12 ` Junio C Hamano
2023-12-20 8:04 ` René Scharfe [this message]
2023-12-20 15:57 ` 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=47089803-c45b-4f33-b542-146c313f0902@web.de \
--to=l.s.r@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).