From: Junio C Hamano <gitster@pobox.com>
To: "René Scharfe" <l.s.r@web.de>
Cc: Git List <git@vger.kernel.org>
Subject: Re: [PATCH] use strvec_pushv() to add another strvec
Date: Thu, 19 Mar 2026 14:14:52 -0700 [thread overview]
Message-ID: <xmqqwlz7iks3.fsf@gitster.g> (raw)
In-Reply-To: <ad46f86f-2ac0-4802-8e63-d854d594932d@web.de> ("René Scharfe"'s message of "Thu, 19 Mar 2026 21:49:05 +0100")
René Scharfe <l.s.r@web.de> writes:
> Simplify the code by letting strvec_pushv() add the items of a second
> strvec instead of pushing them one by one.
>
> Signed-off-by: René Scharfe <l.s.r@web.de>
> ---
> fetch-pack.c | 8 ++------
> git.c | 3 +--
> submodule.c | 4 +---
> 3 files changed, 4 insertions(+), 11 deletions(-)
Nice. Is this something we can make a coccinelle rule for?
Something like
@@
struct strvec SRC;
struct strvec DST;
size_t I;
@@
- for (size_t I = 0; I < SRC.nr; I++)
- strvec_push(&DST, SRC.v[I]);
+ strvec_pushv(&DST, SRC.v);
perhaps?
Will queue.
> diff --git a/fetch-pack.c b/fetch-pack.c
> index 6ecd468ef7..a32224ed02 100644
> --- a/fetch-pack.c
> +++ b/fetch-pack.c
> @@ -1024,12 +1024,8 @@ static int get_pack(struct fetch_pack_args *args,
> fsck_msg_types.buf);
> }
>
> - if (index_pack_args) {
> - int i;
> -
> - for (i = 0; i < cmd.args.nr; i++)
> - strvec_push(index_pack_args, cmd.args.v[i]);
> - }
> + if (index_pack_args)
> + strvec_pushv(index_pack_args, cmd.args.v);
>
> sigchain_push(SIGPIPE, SIG_IGN);
>
> diff --git a/git.c b/git.c
> index 2b212e6675..5a40eab8a2 100644
> --- a/git.c
> +++ b/git.c
> @@ -877,8 +877,7 @@ static int run_argv(struct strvec *args)
> commit_pager_choice();
>
> strvec_push(&cmd.args, "git");
> - for (size_t i = 0; i < args->nr; i++)
> - strvec_push(&cmd.args, args->v[i]);
> + strvec_pushv(&cmd.args, args->v);
>
> trace_argv_printf(cmd.args.v, "trace: exec:");
>
> diff --git a/submodule.c b/submodule.c
> index cd879a5cfe..4c8c674aa4 100644
> --- a/submodule.c
> +++ b/submodule.c
> @@ -1815,7 +1815,6 @@ int fetch_submodules(struct repository *r,
> int default_option,
> int quiet, int max_parallel_jobs)
> {
> - int i;
> struct submodule_parallel_fetch spf = SPF_INIT;
> const struct run_process_parallel_opts opts = {
> .tr2_category = "submodule",
> @@ -1842,8 +1841,7 @@ int fetch_submodules(struct repository *r,
> die(_("index file corrupt"));
>
> strvec_push(&spf.args, "fetch");
> - for (i = 0; i < options->nr; i++)
> - strvec_push(&spf.args, options->v[i]);
> + strvec_pushv(&spf.args, options->v);
> strvec_push(&spf.args, "--recurse-submodules-default");
> /* default value, "--submodule-prefix" and its value are added later */
next prev parent reply other threads:[~2026-03-19 21:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 20:49 [PATCH] use strvec_pushv() to add another strvec René Scharfe
2026-03-19 21:14 ` Junio C Hamano [this message]
2026-03-20 0:46 ` René Scharfe
2026-03-20 0:46 ` [PATCH v2] " René Scharfe
2026-03-22 18:05 ` Junio C Hamano
2026-03-27 23:07 ` René Scharfe
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=xmqqwlz7iks3.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=l.s.r@web.de \
/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