From: Junio C Hamano <gitster@pobox.com>
To: Charles Bailey <charles@hashpling.org>
Cc: git@vger.kernel.org, "Jonas Flodén" <jonas.floden@gmail.com>
Subject: Re: [PATCH 2/2] mergetool: fix running mergetool in sub-directories
Date: Sat, 31 Jan 2009 17:32:45 -0800 [thread overview]
Message-ID: <7v63jv0wn6.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <1233357611-31820-2-git-send-email-charles@hashpling.org> (Charles Bailey's message of "Fri, 30 Jan 2009 23:20:11 +0000")
Charles Bailey <charles@hashpling.org> writes:
> diff --git a/git-mergetool.sh b/git-mergetool.sh
> index aefdca7..87fa88a 100755
> --- a/git-mergetool.sh
> +++ b/git-mergetool.sh
> @@ -13,7 +13,6 @@ SUBDIRECTORY_OK=Yes
> OPTIONS_SPEC=
> . git-sh-setup
> require_work_tree
> -prefix=$(git rev-parse --show-prefix)
>
> # Returns true if the mode reflects a symlink
> is_symlink () {
> @@ -131,7 +130,7 @@ checkout_staged_file () {
> tmpfile=$(expr "$(git checkout-index --temp --stage="$1" "$2")" : '\([^ ]*\) ')
>
> if test $? -eq 0 -a -n "$tmpfile" ; then
> - mv -- "$tmpfile" "$3"
> + mv -- "$(git rev-parse --show-cdup)$tmpfile" "$3"
> fi
> }
Looking at the above change together with this disabled patch in the previous,
> +# We can't merge files from parent directories when running mergetool
> +# from a subdir. Is this a bug?
> +#
> +#test_expect_failure 'mergetool in subdir' '
> +# cd subdir && (
> +# ( yes "" | git mergetool ../file1 >/dev/null 2>&1 ) &&
> +# ( yes "" | git mergetool ../file2 >/dev/null 2>&1 ) &&
> +# test "$(cat ../file1)" = "master updated" &&
> +# test "$(cat ../file2)" = "master new" &&
> +# git commit -m "branch1 resolved with mergetool - subdir" )
> +#'
I wonder if it would be cleaner to keep $prefix and instead cd_to_toplevel
at the beginning.
There are two ways for Porcelain scripts to work from inside a
subdirectory of a project.
* Stay in the original subdirectory and use show-cdup to convert a path
that is relative to the repository root to a path relative to your
current subdirectory.
* Go up to the root of the work tree, use prefix to convert a path that
is relative to the original subdirectory to a path relative to the root
of the work tree.
The former way is probably the clunkier one between the two. I think the
latter is how most of the Porcelain scripts work when they need to worry
about the Plumbing commands that return/accept repository relative paths.
Also, all the plumbing commands work in the latter way.
next prev parent reply other threads:[~2009-02-01 1:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-30 23:20 [PATCH 1/2] mergetool: Add a test for running mergetool in a sub-directory Charles Bailey
2009-01-30 23:20 ` [PATCH 2/2] mergetool: fix running mergetool in sub-directories Charles Bailey
2009-02-01 1:32 ` Junio C Hamano [this message]
2009-02-02 23:19 ` Charles Bailey
2009-02-07 21:48 ` 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=7v63jv0wn6.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=charles@hashpling.org \
--cc=git@vger.kernel.org \
--cc=jonas.floden@gmail.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).