From: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
To: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
Cc: git@vger.kernel.org
Subject: [RFC PATCH] builtin/worktree: enhance worktree removal
Date: Tue, 21 Nov 2017 20:39:54 +0530 [thread overview]
Message-ID: <20171121150954.3227-1-kaartic.sivaraam@gmail.com> (raw)
The new feature to 'remove' worktree was handy to remove specific
worktrees. It didn't cover one particular case of removal. Specifically,
if there is an "entry" (a directory in <main_worktree>/.git/worktrees)
for a worktree but the worktree repository itself does not exist then
it means that the "entry" is stale and it could just be removed.
So, in case there's a "worktree entry" but not "worktree direectory"
then just remove the 'stale' entry.
Signed-off-by: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
---
Hello Duy,
I noticed that your remove command could be enhanced for a particular
case. So, I made up an ad-hoc patch "illustrating" how it could be done.
I may have broken something by quieting out 'validate_worktree()'
function, so take note of it.
You might add this as a separate commit or just incorporate it into
one of your commits if you re-roll your 'nd/worktree-move' branch.
Thanks,
Kaartic
builtin/worktree.c | 38 ++++++++++++++++++++++++++++----------
1 file changed, 28 insertions(+), 10 deletions(-)
diff --git a/builtin/worktree.c b/builtin/worktree.c
index b5afba164..f70bc0bd8 100644
--- a/builtin/worktree.c
+++ b/builtin/worktree.c
@@ -605,6 +605,22 @@ static int move_worktree(int ac, const char **av, const char *prefix)
return update_worktree_location(wt, dst.buf);
}
+/* Removes the .git/worktrees/worktree_id directory for
+ the given worktree_id
+
+ Returns 0 on success and non-zero value in case of failure */
+static int remove_worktree_entry(char *worktree_id) {
+ int ret = 0;
+ struct strbuf we_path = STRBUF_INIT;
+ strbuf_addstr(&we_path, git_common_path("worktrees/%s", worktree_id));
+ if (remove_dir_recursively(&we_path, 0)) {
+ error_errno(_("failed to delete '%s'"), we_path.buf);
+ ret = -1;
+ }
+ strbuf_release(&we_path);
+ return ret;
+}
+
static int remove_worktree(int ac, const char **av, const char *prefix)
{
int force = 0;
@@ -634,9 +650,17 @@ static int remove_worktree(int ac, const char **av, const char *prefix)
die(_("already locked, reason: %s"), reason);
die(_("already locked, no reason"));
}
- if (validate_worktree(wt, 0))
- return -1;
-
+ if (validate_worktree(wt, 1)) {
+ if (!file_exists(wt->path)) {
+ /* There's a worktree entry but the worktree directory
+ doesn't exist. So, just remove the worktree entry. */
+ ret = remove_worktree_entry(wt->id);
+ free_worktrees(worktrees);
+ return ret;
+ } else {
+ return -1;
+ }
+ }
if (!force) {
struct argv_array child_env = ARGV_ARRAY_INIT;
struct child_process cp;
@@ -670,13 +694,7 @@ static int remove_worktree(int ac, const char **av, const char *prefix)
error_errno(_("failed to delete '%s'"), sb.buf);
ret = -1;
}
- strbuf_reset(&sb);
- strbuf_addstr(&sb, git_common_path("worktrees/%s", wt->id));
- if (remove_dir_recursively(&sb, 0)) {
- error_errno(_("failed to delete '%s'"), sb.buf);
- ret = -1;
- }
- strbuf_release(&sb);
+ ret = remove_worktree_entry(wt->id);
free_worktrees(worktrees);
return ret;
}
--
2.15.0.345.gf926f18f3
next reply other threads:[~2017-11-21 15:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-21 15:09 Kaartic Sivaraam [this message]
2017-11-21 21:37 ` [RFC PATCH] builtin/worktree: enhance worktree removal Eric Sunshine
2017-11-22 2:12 ` Junio C Hamano
2017-11-22 3:14 ` Eric Sunshine
2017-11-22 3:23 ` Eric Sunshine
2017-11-22 3:55 ` Junio C Hamano
2017-11-22 4:37 ` Eric Sunshine
2017-11-22 17:51 ` Kaartic Sivaraam
2017-11-27 17:36 ` [RFC PATCH v2] " Kaartic Sivaraam
2017-11-28 3:02 ` Junio C Hamano
2017-11-28 3:48 ` Eric Sunshine
2017-11-28 4:04 ` Junio C Hamano
2017-11-28 6:02 ` Eric Sunshine
2017-11-28 16:46 ` Kaartic Sivaraam
2017-11-22 17:13 ` [RFC PATCH] " Kaartic Sivaraam
2017-11-22 17:09 ` Kaartic Sivaraam
2017-11-22 18:05 ` Eric Sunshine
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=20171121150954.3227-1-kaartic.sivaraam@gmail.com \
--to=kaartic.sivaraam@gmail.com \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.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).