git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: "David Kågedal" <davidk@lysator.liu.se>
Cc: git@vger.kernel.org
Subject: Re: Removing files
Date: Thu, 11 Jan 2007 15:36:18 -0800	[thread overview]
Message-ID: <7vzm8p16h9.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <7vejq12nlu.fsf@assigned-by-dhcp.cox.net> (Junio C. Hamano's message of "Thu, 11 Jan 2007 14:41:01 -0800")

Junio C Hamano <junkio@cox.net> writes:

> I think the right fix is to suggest "git add/rm" in status
> output and make "git rm" not barf if the user has already
> removed the file from the working tree.

This does the latter.  A separate patch will do the former.

-- >8 --

[PATCH] git-rm: do not fail on already removed file.

Often the user would do "/bin/rm foo" before telling git, but
then want to tell git about it.  "git rm foo" however would fail
because it cannot unlink(2) foo.

Treat ENOENT error return from unlink(2) as if a successful
removal happened.

Signed-off-by: Junio C Hamano <junkio@cox.net>
---
 builtin-rm.c |    6 +++++-
 1 files changed, 5 insertions(+), 1 deletions(-)

diff --git a/builtin-rm.c b/builtin-rm.c
index 5b078c4..d81f289 100644
--- a/builtin-rm.c
+++ b/builtin-rm.c
@@ -32,6 +32,10 @@ static int remove_file(const char *name)
 	char *slash;
 
 	ret = unlink(name);
+	if (ret && errno == ENOENT)
+		/* The user has removed it from the filesystem by hand */
+		ret = errno = 0;
+
 	if (!ret && (slash = strrchr(name, '/'))) {
 		char *n = xstrdup(name);
 		do {
@@ -204,7 +208,7 @@ int cmd_rm(int argc, const char **argv, const char *prefix)
 		return 0;
 
 	/*
-	 * Then, unless we used "--cache", remove the filenames from
+	 * Then, unless we used "--cached", remove the filenames from
 	 * the workspace. If we fail to remove the first one, we
 	 * abort the "git rm" (but once we've successfully removed
 	 * any file at all, we'll go ahead and commit to it all:
-- 
1.4.4.4.gb8a1

  parent reply	other threads:[~2007-01-11 23:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-11 20:10 Removing files David Kågedal
2007-01-11 21:36 ` Alex Riesen
2007-01-11 22:25   ` Seth Falcon
2007-01-11 22:41 ` Junio C Hamano
2007-01-11 23:19   ` Eric Wong
2007-01-11 23:36   ` Junio C Hamano [this message]
2007-01-11 23:37   ` [PATCH] git-status: wording update to deal with deleted files Junio C Hamano
2007-01-11 23:56     ` Carl Worth
2007-01-12  0:13       ` Junio C Hamano
2007-01-12  1:28         ` Carl Worth
2007-01-12 19:48           ` Jakub Narebski
2007-01-12  0:07     ` Jeff King
2007-01-12 22:13     ` Juergen Ruehle
2007-01-11 23:41 ` Removing files Carl Worth
2007-01-12  0:17   ` Jeff King

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=7vzm8p16h9.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=davidk@lysator.liu.se \
    --cc=git@vger.kernel.org \
    /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).