From: Junio C Hamano <gitster@pobox.com>
To: David Kastrup <dak@gnu.org>
Cc: git@vger.kernel.org, Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: [fixed PATCH] git-filter-branch.sh: Fix broken setting of GIT_DIR
Date: Sat, 11 Aug 2007 03:06:36 -0700 [thread overview]
Message-ID: <7vk5s2mllf.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <864pj74ay9.fsf@lola.quinscape.zz> (David Kastrup's message of "Fri, 10 Aug 2007 18:21:34 +0200")
David Kastrup <dak@gnu.org> writes:
> If filter-branch is entered with an unset GIT_DIR, things are rather
> fragile. The GIT_DIR variable setting then points to something like
> $(pwd)/../.. which is neither guaranteed to be a git directory
I think this comment refers to this part, ...
> -case "$GIT_DIR" in
> -/*)
> - ;;
> -*)
> - GIT_DIR="$(pwd)/../../$GIT_DIR"
> - ;;
> -esac
... however, at the beginning of the script, it dot-includes
git-sh-setup, which sets (but not export) GIT_DIR for the rest
of the script to use (see the last if..then..else).
If you got an unset GIT_DIR when you reached that case statement
you are removing here, I suspect that there is something else
going on, but I do not see what it is...
Puzzled...
next prev parent reply other threads:[~2007-08-11 10:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-10 14:02 [PATCH] git-filter-branch.sh: Fix broken setting of GIT_DIR David Kastrup
2007-08-10 16:21 ` [fixed PATCH] " David Kastrup
2007-08-11 10:06 ` Junio C Hamano [this message]
2007-08-11 10:32 ` David Kastrup
2007-08-11 12:12 ` David Kastrup
2007-08-11 12:29 ` David Kastrup
2007-08-11 19:53 ` Junio C Hamano
2007-08-11 21:04 ` David Kastrup
2007-08-11 22:02 ` [PATCH] Add a test for git-commit being confused by relative GIT_DIR David Kastrup
2007-08-12 1:55 ` Junio C Hamano
2007-08-12 6:47 ` David Kastrup
2007-08-12 17:05 ` Junio C Hamano
2007-08-12 18:44 ` David Kastrup
2007-08-11 12:51 ` [fixed PATCH] git-filter-branch.sh: Fix broken setting of GIT_DIR Steven Grimm
2007-08-11 20:10 ` Junio C Hamano
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=7vk5s2mllf.fsf@assigned-by-dhcp.cox.net \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=dak@gnu.org \
--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