From: David Aguilar <davvid@gmail.com>
To: Charles Bailey <charles@hashpling.org>
Cc: Junio C Hamano <gitster@pobox.com>,
"git@vger.kernel.org" <git@vger.kernel.org>,
Charles Bailey <cbailey32@bloomberg.net>
Subject: Re: [PATCH v2 1/2] mergetool: don't require a work tree for --tool-help
Date: Sat, 11 Oct 2014 01:29:56 -0700 [thread overview]
Message-ID: <20141011082954.GA79450@gmail.com> (raw)
In-Reply-To: <FCAAE5E4-E220-4B45-A6A1-B2AFB79F9069@hashpling.org>
On Fri, Oct 10, 2014 at 10:01:57AM +0100, Charles Bailey wrote:
> On 10 Oct 2014, at 09:51, David Aguilar <davvid@gmail.com> wrote:
> > Changes since v1:
> >
> > NONGIT_OK=Yes was added to make it actually work outside of a git repo.
>
> Does this actually work? The reason that I haven't got around
> to resending my re-roll is that I found that I needed changes
> to git-sh-setup.sh because doing NONGIT_OK and then
> require_work_tree didn't correctly set GIT_DIR when it wasn't
> already explicitly set in the environment. (I believe the rest
> of mergetool relies on it.)
>
> Perhaps I misunderstood, though.
Thanks for the heads-up.
I tested mergetool and it seems fine but indeed there's an
`if test -e "$GIT_DIR/MERGE_RR"` in there that is surely not
working as intended.
One solution would be to move the work done in the test -z "$NONGIT_OK"
block in git-sh-setup into a function e.g. git_dir_init () so
that we can defer the GIT_DIR initialization until after
require_work_tree has been called.
--
David
next prev parent reply other threads:[~2014-10-11 8:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-10 8:51 [PATCH v2 1/2] mergetool: don't require a work tree for --tool-help David Aguilar
2014-10-10 8:51 ` [PATCH v2 2/2] difftool: don't assume that default sh is sane David Aguilar
2014-10-10 9:01 ` [PATCH v2 1/2] mergetool: don't require a work tree for --tool-help Charles Bailey
2014-10-11 8:29 ` David Aguilar [this message]
2014-10-11 8:35 ` Charles Bailey
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=20141011082954.GA79450@gmail.com \
--to=davvid@gmail.com \
--cc=cbailey32@bloomberg.net \
--cc=charles@hashpling.org \
--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).