From: Thomas Rast <trast@student.ethz.ch>
To: David Aguilar <davvid@gmail.com>
Cc: "Junio C Hamano" <gitster@pobox.com>,
git@vger.kernel.org, "Magnus Bäck" <magnus.back@sonyericsson.com>,
"Charles Bailey" <charles@hashpling.org>,
"Avery Pennarun" <apenwarr@gmail.com>
Subject: Re: [PATCH] mergetool: Skip autoresolved paths
Date: Thu, 19 Aug 2010 12:02:36 +0200 [thread overview]
Message-ID: <201008191202.36508.trast@student.ethz.ch> (raw)
In-Reply-To: <1282036966-26799-1-git-send-email-davvid@gmail.com>
David Aguilar wrote:
> When mergetool is run without path limiters it loops
> over each entry in 'git ls-files -u'. This includes
> autoresolved paths.
[...]
> +test_expect_success 'mergetool merges all from subdir' '
> + cd subdir && (
> + git config rerere.enabled false &&
> + test_must_fail git merge master &&
> + git mergetool --no-prompt &&
> + test "$(cat ../file1)" = "master updated" &&
> + test "$(cat ../file2)" = "master new" &&
> + test "$(cat file3)" = "master new sub" &&
> + git add ../file1 ../file2 file3 &&
> + git commit -m "branch2 resolved by mergetool from subdir") &&
> + cd ..
> +'
This test never worked in my automatic testing (it fails and bisects
to this commit).
It might be because the cronjob doesn't have a tty, as I'm seeing the
output below (note the error at the end). Any insights?
expecting success:
cd subdir && (
git config rerere.enabled false &&
test_must_fail git merge master &&
git mergetool --no-prompt &&
test "$(cat ../file1)" = "master updated" &&
test "$(cat ../file2)" = "master new" &&
test "$(cat file3)" = "master new sub" &&
git add ../file1 ../file2 file3 &&
git commit -m "branch2 resolved by mergetool from subdir") &&
cd ..
Merging:
a8bf666 branch1 changes
virtual master
found 1 common ancestor(s):
775c381 added file1
Auto-merging file1
CONFLICT (content): Merge conflict in file1
Auto-merging file2
CONFLICT (add/add): Merge conflict in file2
Auto-merging subdir/file3
CONFLICT (content): Merge conflict in subdir/file3
Automatic merge failed; fix conflicts and then commit the result.
Merging:
file1
file2
subdir/file3
/local/home/trast/git/t/valgrind/bin/git-mergetool: line 302: /dev/tty: No such device
or address
/local/home/trast/git/t/valgrind/bin/git-mergetool: line 299: /dev/tty: No such device
or address
--
Thomas Rast
trast@{inf,student}.ethz.ch
next prev parent reply other threads:[~2010-08-19 10:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-12 21:28 Status of conflicted files resolved with rerere Magnus Bäck
2010-08-12 21:36 ` Avery Pennarun
2010-08-13 17:19 ` Jay Soffian
2010-08-15 2:24 ` David Aguilar
2010-08-15 6:59 ` Junio C Hamano
2010-08-15 16:00 ` Magnus Bäck
2010-08-17 9:22 ` [PATCH] mergetool: Skip autoresolved paths David Aguilar
2010-08-19 10:02 ` Thomas Rast [this message]
2010-08-20 3:52 ` David Aguilar
2010-08-20 9:57 ` Charles Bailey
2010-08-20 10:09 ` Jonathan Nieder
2010-08-20 11:17 ` [PATCH] mergetool: Remove explicit references to /dev/tty Charles Bailey
2010-08-20 12:27 ` Jonathan Nieder
2010-08-20 13:50 ` Charles Bailey
2010-08-20 14:19 ` Jonathan Nieder
2010-08-20 15:25 ` [PATCH v2] " 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=201008191202.36508.trast@student.ethz.ch \
--to=trast@student.ethz.ch \
--cc=apenwarr@gmail.com \
--cc=charles@hashpling.org \
--cc=davvid@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=magnus.back@sonyericsson.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).