From: Santi <sbejar@gmail.com>
To: git@vger.kernel.org, "Junio C Hamano" <junkio@cox.net>
Subject: Re: Merge with local conflicts in new files
Date: Wed, 17 May 2006 00:12:31 +0200 [thread overview]
Message-ID: <8aa486160605161512g4d38b7f0y@mail.gmail.com> (raw)
In-Reply-To: <8aa486160605161500m1dd8428cj@mail.gmail.com>
Sorry, the test is wrong. Use this:
test_description='Test merge with local conflicts in new files'
. ./test-lib.sh
test_expect_success 'prepare repository' \
'echo "Hello" > init &&
git add init &&
git commit -m "Initial commit" &&
git checkout -b B &&
echo "foo" > foo &&
git add foo &&
git commit -m "File: foo" &&
git checkout master &&
echo "bar" > foo &&
'
test_expect_code 1 'Merge with local conflicts in new files' 'git
merge "merge msg" HEAD B'
test_done
next prev parent reply other threads:[~2006-05-16 22:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-16 22:00 Merge with local conflicts in new files Santi
2006-05-16 22:12 ` Santi [this message]
2006-05-16 22:40 ` Junio C Hamano
2006-05-16 23:11 ` Santi
2006-05-16 23:28 ` Junio C Hamano
2006-05-17 7:47 ` Pavel Roskin
2006-05-17 8:20 ` Junio C Hamano
2006-05-17 8:50 ` Martin Langhoff
2006-05-17 8:17 ` [PATCH/RFC] read-tree -m -u: do not overwrite or remove untracked working tree files Junio C Hamano
2006-05-17 8:24 ` Jakub Narebski
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=8aa486160605161512g4d38b7f0y@mail.gmail.com \
--to=sbejar@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).