From: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
To: pclouds@gmail.com
Cc: git@vger.kernel.org, hi-angel@yandex.ru, sunshine@sunshineco.com
Subject: [PATCH v2 0/1] worktree add: sanitize worktree names
Date: Thu, 21 Feb 2019 19:19:42 +0700 [thread overview]
Message-ID: <20190221121943.19778-1-pclouds@gmail.com> (raw)
In-Reply-To: <20190221110026.23135-1-pclouds@gmail.com>
v2 fixes bad ".lock" handling in v1. I keep the "name->len == 0" part
though because I found another valid case that could end up there.
Nguyễn Thái Ngọc Duy (1):
worktree add: sanitize worktree names
builtin/worktree.c | 51 ++++++++++++++++++++++++++++++++++++++++-
t/t2025-worktree-add.sh | 7 ++++++
2 files changed, 57 insertions(+), 1 deletion(-)
Range-diff dựa trên v1:
1: 42a3144874 ! 1: d1b6e1c55b worktree add: sanitize worktree names
@@ -13,7 +13,7 @@
be able to specify the worktree name by themselves if they're not
happy with this dumb character substitution.
- Reported-by: hi-angel@yandex.ru
+ Reported-by: Konstantin Kharlamov <hi-angel@yandex.ru>
Signed-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com>
diff --git a/builtin/worktree.c b/builtin/worktree.c
@@ -30,16 +30,14 @@
+ */
+static void sanitize_worktree_name(struct strbuf *name)
+{
++ char *orig_name = xstrdup(name->buf);
+ int i;
+
-+ /* no ending with .lock */
-+ if (ends_with(name->buf, ".lock"))
-+ strbuf_remove(name, name->len - strlen(".lock"),
-+ strlen(".lock"));
-+
+ /*
+ * All special chars replaced with dashes. See
+ * check_refname_component() for reference.
++ * Note that .lock is also turned to -lock, removing its
++ * special status.
+ */
+ for (i = 0; i < name->len; i++) {
+ if (strchr(":?[]\\~ \t@{}*/.", name->buf[i]))
@@ -55,12 +53,18 @@
+ strbuf_remove(name, i, 1);
+ }
+
-+ /* last resort, should never ever happen in practice */
++ /*
++ * a worktree name of only special chars would be reduced to
++ * an empty string
++ */
+ if (name->len == 0)
+ strbuf_addstr(name, "worktree");
+
+ if (check_refname_format(name->buf, REFNAME_ALLOW_ONELEVEL))
-+ BUG("worktree name '%s' is not a valid refname", name->buf);
++ BUG("worktree name '%s' (from '%s') is not a valid refname",
++ name->buf, orig_name);
++
++ free(orig_name);
+}
+
static int add_worktree(const char *path, const char *refname,
@@ -103,8 +107,10 @@
'
+test_expect_success 'sanitize generated worktree name' '
-+ git worktree add --detach ". weird*..?.lock" &&
-+ test -d .git/worktrees/weird
++ git worktree add --detach ". weird*..?.lock.lock" &&
++ test -d .git/worktrees/weird-lock-lock &&
++ git worktree add --detach .... &&
++ test -d .git/worktrees/worktree
+'
+
test_done
--
2.21.0.rc1.337.gdf7f8d0522
next prev parent reply other threads:[~2019-02-21 12:20 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 14:36 git gc fails with "unable to resolve reference" for worktree hi-angel
2019-02-18 15:02 ` Duy Nguyen
2019-02-18 15:09 ` hi-angel
2019-02-18 15:18 ` Duy Nguyen
2019-02-20 14:34 ` hi-angel
2019-02-21 11:00 ` [PATCH] worktree add: sanitize worktree names Nguyễn Thái Ngọc Duy
2019-02-21 11:28 ` Konstantin Kharlamov
2019-02-21 11:38 ` Duy Nguyen
2019-02-21 11:44 ` Konstantin Kharlamov
2019-02-21 11:52 ` Duy Nguyen
2019-02-21 13:23 ` Jeff King
2019-02-21 12:19 ` Nguyễn Thái Ngọc Duy [this message]
2019-02-21 12:19 ` [PATCH v2 1/1] " Nguyễn Thái Ngọc Duy
2019-02-21 13:22 ` Jeff King
2019-02-21 17:41 ` Ramsay Jones
2019-02-22 9:21 ` Duy Nguyen
2019-02-26 10:58 ` [PATCH v3 0/1] " Nguyễn Thái Ngọc Duy
2019-02-26 10:58 ` [PATCH v3 1/1] " Nguyễn Thái Ngọc Duy
2019-02-27 12:08 ` Jeff King
2019-02-27 14:23 ` Eric Sunshine
2019-02-27 16:04 ` Jeff King
2019-03-03 1:22 ` Junio C Hamano
2019-03-04 11:19 ` Duy Nguyen
2019-03-04 12:04 ` Duy Nguyen
2019-03-04 15:06 ` Johannes Schindelin
2019-03-05 12:08 ` [PATCH v4 0/2] " Nguyễn Thái Ngọc Duy
2019-03-05 12:08 ` [PATCH v4 1/2] refs.c: refactor check_refname_component() Nguyễn Thái Ngọc Duy
2019-03-06 21:49 ` Jeff King
2019-03-07 23:24 ` Eric Sunshine
2019-03-05 12:08 ` [PATCH v4 2/2] worktree add: sanitize worktree names Nguyễn Thái Ngọc Duy
2019-03-08 9:28 ` [PATCH v5 0/1] " Nguyễn Thái Ngọc Duy
2019-03-08 9:28 ` [PATCH v5 1/1] " Nguyễn Thái Ngọc Duy
2019-03-10 2:02 ` Eric Sunshine
2019-03-11 6:20 ` Junio C Hamano
2019-03-11 9:24 ` Duy Nguyen
2019-03-11 22:39 ` Jeff King
2019-03-12 6:32 ` Junio C Hamano
2019-03-11 6:36 ` Junio C Hamano
2019-03-11 9:27 ` Duy Nguyen
2019-03-11 13:05 ` Johannes Schindelin
2019-03-12 6:45 ` 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190221121943.19778-1-pclouds@gmail.com \
--to=pclouds@gmail.com \
--cc=git@vger.kernel.org \
--cc=hi-angel@yandex.ru \
--cc=sunshine@sunshineco.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).