From: Pavel Roskin <proski@gnu.org>
To: Petr Baudis <pasky@suse.cz>
Cc: git <git@vger.kernel.org>
Subject: [PATCH] cg-seek should not complain if run twice
Date: Mon, 19 Dec 2005 23:55:36 -0500 [thread overview]
Message-ID: <1135054536.3815.14.camel@dv> (raw)
cg-seek complains if run without arguments in a non-seeked repository:
rm: cannot remove `.git/refs/heads/cg-seek-point': No such file or directory
rm: cannot remove `.git/head-name': No such file or directory
In fact, it's OK for those files not to exist, so they should be removed
silently.
Signed-off-by: Pavel Roskin <proski@gnu.org>
diff --git a/cg-seek b/cg-seek
index 942267f..8356593 100755
--- a/cg-seek
+++ b/cg-seek
@@ -60,7 +60,7 @@ if [ "$seek_mode" = "away" ]; then
git-symbolic-ref HEAD "refs/heads/cg-seek-point"
else
git-symbolic-ref HEAD "refs/heads/$_git_head"
- rm "$_git/refs/heads/cg-seek-point" "$_git/head-name"
+ rm -f "$_git/refs/heads/cg-seek-point" "$_git/head-name"
rm -f "$_git/blocked"
fi
--
Regards,
Pavel Roskin
next reply other threads:[~2005-12-20 4:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-20 4:55 Pavel Roskin [this message]
2006-01-14 23:30 ` [PATCH] cg-seek should not complain if run twice Petr Baudis
2006-01-15 6:03 ` Pavel Roskin
2006-01-15 23:59 ` Petr Baudis
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=1135054536.3815.14.camel@dv \
--to=proski@gnu.org \
--cc=git@vger.kernel.org \
--cc=pasky@suse.cz \
/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).