From: Patrick Steinhardt <ps@pks.im>
To: Joaquim Rocha via GitGitGadget <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Joaquim Rocha <me@joaquimrocha.com>,
Joaquim Rocha <joaquim@amutable.com>
Subject: Re: [PATCH] apply: strip ./ prefix from --directory argument
Date: Tue, 17 Feb 2026 09:06:52 +0100 [thread overview]
Message-ID: <aZQhnIcPa9sCPpBb@pks.im> (raw)
In-Reply-To: <pull.2198.git.git.1771002510709.gitgitgadget@gmail.com>
On Fri, Feb 13, 2026 at 05:08:30PM +0000, Joaquim Rocha via GitGitGadget wrote:
> From: Joaquim Rocha <joaquim@amutable.com>
>
> When passing a relative path like --directory=./some/sub, the leading
> "./" caused apply to prepend it literally to patch filenames, resulting
> in an error (invalid path).
>
> Since using "./" is almost memory muscle for many, strip the "./"
> prefix so it behaves the same as --directory=some/sub.
Isn't the problem wider than that though? For example, if you had
"././some/sub" it would break again. Or if you had "some/./sub", or
"some/sub/../sub", or "some//sub".
> diff --git a/apply.c b/apply.c
> index 3de4aa4d2e..a44c54077c 100644
> --- a/apply.c
> +++ b/apply.c
> @@ -5001,6 +5001,10 @@ static int apply_option_parse_directory(const struct option *opt,
> BUG_ON_OPT_NEG(unset);
>
> strbuf_reset(&state->root);
> +
> + if (starts_with(arg, "./"))
> + arg += 2;
> +
> strbuf_addstr(&state->root, arg);
> strbuf_complete(&state->root, '/');
> return 0;
While this change here fixes your observed issues, the next person might
run into a totally different one. So more generally, I think what we'd
rather want to do is to fully normalize the path. How about this
instead:
diff --git a/apply.c b/apply.c
index 9de2eb953e..8946b133a3 100644
--- a/apply.c
+++ b/apply.c
@@ -5002,6 +5002,7 @@ static int apply_option_parse_directory(const struct option *opt,
strbuf_reset(&state->root);
strbuf_addstr(&state->root, arg);
+ strbuf_normalize_path(&state->root);
strbuf_complete(&state->root, '/');
return 0;
}
`strbuf_normalize_path()` drops "." components, removes ".." and it
squashes multiple directory separators. So it handles your specific use
case, but also others.
Thanks!
Patrick
next prev parent reply other threads:[~2026-02-17 8:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-13 17:08 [PATCH] apply: strip ./ prefix from --directory argument Joaquim Rocha via GitGitGadget
2026-02-17 8:06 ` Patrick Steinhardt [this message]
2026-02-17 20:27 ` Junio C Hamano
2026-02-18 14:14 ` Patrick Steinhardt
2026-02-18 14:40 ` Joaquim Rocha
2026-02-18 0:15 ` [PATCH v2] apply: normalize path in " Joaquim Rocha via GitGitGadget
2026-02-20 20:26 ` 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=aZQhnIcPa9sCPpBb@pks.im \
--to=ps@pks.im \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=joaquim@amutable.com \
--cc=me@joaquimrocha.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