From: Jonathan Nieder <jrnieder@gmail.com>
To: Clemens Buchacher <drizzd@aon.at>
Cc: git@vger.kernel.org, "Junio C Hamano" <gitster@pobox.com>,
"Frédéric Brière" <fbriere@fbriere.net>
Subject: Re: [PATCH] setup: do not change to work tree prematurely
Date: Sat, 22 May 2010 20:35:39 -0500 [thread overview]
Message-ID: <20100523013539.GA14403@progeny.tock> (raw)
In-Reply-To: <20100523000719.GA32380@localhost>
Hi Clemens,
Clemens Buchacher wrote:
> $ cd .git
> $ git --work-tree=/tmp/git symbolic-ref HEAD
> fatal: ref HEAD is not a symbolic ref
Without your patch applied, I get
$ cd .git
$ git --work-tree=/tmp/git symbolic-ref HEAD
refs/heads/hello
I should have done the following instead:
$ worktree=$(pwd)
$ cd .git
$ git --work-tree="$worktree" symbolic-ref HEAD
fatal: ref HEAD is not a symbolic ref
> +char *get_relative_path(char *cwd, const char *dir)
Looks reasonable. Should be const char *cwd.
> diff --git a/setup.c b/setup.c
> index 5716d90..67b5122 100644
> --- a/setup.c
> +++ b/setup.c
> @@ -524,14 +524,18 @@ const char *setup_git_directory(void)
> const char *retval = setup_git_directory_gently(NULL);
>
> /* If the work tree is not the default one, recompute prefix */
> if (inside_work_tree < 0) {
If I understand correctly, you made two changes here:
- interpret GIT_WORK_TREE and friends relative to .git instead of
the original cwd (by not calling chdir(retval) before
get_git_work_tree())
- make setup_git_directory stay in the last directory searched for a
.git directory instead of chdir-ing into the toplevel of the work tree.
Are these safe changes to make?
Jonathan
diff --git a/t/t1501-worktree.sh b/t/t1501-worktree.sh
index 9df3012..93bf92c 100755
--- a/t/t1501-worktree.sh
+++ b/t/t1501-worktree.sh
@@ -106,6 +106,15 @@ test_expect_success 'repo finds its work tree from work tree, too' '
test sub/dir/tracked = "$(git ls-files)")
'
+test -d work || cp -R repo.git/work .
+test_expect_success 'repo finds its .git dir with separate worktree' '
+ (unset GIT_DIR GIT_WORK_TREE GIT_CONFIG &&
+ worktree=$(pwd) &&
+ cd repo.git &&
+ git symbolic-ref HEAD &&
+ git --work-tree="$worktree" symbolic-ref HEAD)
+'
+
test_expect_success '_gently() groks relative GIT_DIR & GIT_WORK_TREE' '
(cd repo.git/work/sub/dir &&
GIT_DIR=../../.. GIT_WORK_TREE=../.. GIT_PAGER= \
--
next prev parent reply other threads:[~2010-05-23 1:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-23 0:07 [PATCH] setup: do not change to work tree prematurely Clemens Buchacher
2010-05-23 1:35 ` Jonathan Nieder [this message]
2010-05-23 9:14 ` Clemens Buchacher
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=20100523013539.GA14403@progeny.tock \
--to=jrnieder@gmail.com \
--cc=drizzd@aon.at \
--cc=fbriere@fbriere.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
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).