From: Jim Meyering <jim@meyering.net>
To: git@vger.kernel.org
Subject: "cg-commit -M msg-file ..." fails when not run from top of tree
Date: Wed, 23 Aug 2006 12:27:38 +0200 [thread overview]
Message-ID: <87d5aru4px.fsf@rho.meyering.net> (raw)
Hello,
I discovered that "cg-commit -M MSG-FILE ..." fails when run from
a subdirectory, and when MSG-FILE is a relative file name.
This is using cogito-0.17.3-2 from Debian/unstable, but the problem
remains when using the latest cogito sources, pulled minutes ago.
Here's an example:
$ mkdir a; touch a/x; cg-init -m. .; cd a; echo . > x; cg-commit -M x x
defaulting to local storage area
Adding file a/x
Committing initial tree 341d89829a1bf9c0ccfbccf738815cbc862b3242
Committed as 6497164c6f8e86220ff26c6b89b9d0dbad5a7743
cat: x: No such file or directory
[Exit 1]
This appears to be due to the "cd", that can happen in cg-Xlib:
_git="${GIT_DIR:-.git}"
if [ ! "$_git_repo_unneeded" ] && [ ! "$GIT_DIR" ] && [ ! -d "$_git" ]; then
_git_abs_path="$(git-rev-parse --git-dir 2>/dev/null)"
if [ -d "$_git_abs_path" ]; then
_git_relpath="$(git-rev-parse --show-prefix)"
==========> cd "$_git_abs_path/.." <==============
fi
fi
_git_objects="${GIT_OBJECT_DIRECTORY:-$_git/objects}"
I can work around the problem by using an absolute name for
the message file, but I shouldn't have to do that.
FWIW, I tried setting GIT_DIR to the absolute name of the .git directory,
but that just made it so cg-commit failed with this diagnostic:
cg-commit: Nothing to commit
Jim
next reply other threads:[~2006-08-23 10:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-23 10:27 Jim Meyering [this message]
2006-08-25 0:06 ` [PATCH] cg-commit: prefix the relative path to the message file Jonas Fonseca
2006-09-16 15:07 ` Jim Meyering
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=87d5aru4px.fsf@rho.meyering.net \
--to=jim@meyering.net \
--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).