From: koreth@midwinter.com
To: git@vger.kernel.org
Subject: [PATCH] Change git-rev-parse --show-cdup to output an absolute path
Date: Wed, 25 Apr 2007 16:28:29 -0700 [thread overview]
Message-ID: <20070425232829.GA15930@midwinter.com> (raw)
Add a test case for deep symlinking into a repo, which breaks with the
old relative output of --show-cdup.
Signed-off-by: Steven Grimm <koreth@midwinter.com>
---
I have a symlink pointing to a subdirectory of a repo of mine. If I cd
to that symlink, some shell-script git commands don't work. Shell scripts
use the PWD environment variable as the working directory, and the chain
of "../"s from git-rev-parse --show-cdup just peels entries off that
variable. That's fine when PWD is a real path, but not so great when it's
a reference to a symlink from an outside directory.
A typical failure case:
$ git clone git://whatever.git foobar
$ ln -s foobar/src/tools/misc/myapp myapp
$ cd myapp
$ git pull
fatal: Not a git repository
This patch adds a test for the problem (fails in the current git build)
and a proposed fix: making git-rev-parse --show-cdup output an absolute
path. It's possible that'll break something somewhere, but all the tests
in the test suite pass, so I think the breakage can't be *too* severe if
there's any at all.
builtin-rev-parse.c | 18 +++++++++---------
t/t6102-rev-parse-cdup.sh | 24 ++++++++++++++++++++++++
2 files changed, 33 insertions(+), 9 deletions(-)
create mode 100755 t/t6102-rev-parse-cdup.sh
diff --git a/builtin-rev-parse.c b/builtin-rev-parse.c
index 37addb2..99a95eb 100644
--- a/builtin-rev-parse.c
+++ b/builtin-rev-parse.c
@@ -320,15 +320,15 @@ int cmd_rev_parse(int argc, const char **argv, const char *prefix)
continue;
}
if (!strcmp(arg, "--show-cdup")) {
- const char *pfx = prefix;
- while (pfx) {
- pfx = strchr(pfx, '/');
- if (pfx) {
- pfx++;
- printf("../");
- }
- }
- putchar('\n');
+ char cwd[PATH_MAX];
+ /*
+ * The prefix computation does chdir("..") until it
+ * reaches the top level, so the current directory
+ * is actually the thing we want to output.
+ */
+ if (!getcwd(cwd, PATH_MAX))
+ die("unable to get current working directory");
+ printf("%s/\n", cwd);
continue;
}
if (!strcmp(arg, "--git-dir")) {
diff --git a/t/t6102-rev-parse-cdup.sh b/t/t6102-rev-parse-cdup.sh
new file mode 100755
index 0000000..233d9cf
--- /dev/null
+++ b/t/t6102-rev-parse-cdup.sh
@@ -0,0 +1,24 @@
+#!/bin/sh
+#
+# Copyright (c) 2007 Steven Grimm
+#
+
+test_description='Test git-rev-parse --show-cdup'
+
+. ./test-lib.sh
+. ../t6000lib.sh # t6xxx specific functions
+
+# Make a subdirectory and a symbolic link pointing to it from outside the repo.
+mkdir subdir
+ln -s `pwd`/subdir /tmp/git-test.$$
+cd /tmp/git-test.$$
+
+test_expect_success 'shell pwd references symlink' "pwd | grep git-test.$$"
+test_expect_success 'cdup goes to top level of repo' '
+ cd `git-rev-parse --show-cdup` &&
+ test -d .git'
+
+rm /tmp/git-test.$$
+
+test_done
+
--
1.5.2.rc0.1.g2cc31
next reply other threads:[~2007-04-25 23:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-25 23:28 koreth [this message]
2007-04-26 8:20 ` [PATCH] Change git-rev-parse --show-cdup to output an absolute path Alex Riesen
2007-04-26 9:00 ` Steven Grimm
2007-04-26 9:12 ` [PATCH] Use PATH_MAX rather than a hardwired constant maximum length koreth
2007-04-26 12:14 ` Alex Riesen
2007-04-26 11:57 ` [PATCH] Change git-rev-parse --show-cdup to output an absolute path Alex Riesen
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=20070425232829.GA15930@midwinter.com \
--to=koreth@midwinter.com \
--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).