From: Eric Raible <raible@gmail.com>
To: git@vger.kernel.org
Subject: Poor status output during conflicted merge
Date: Thu, 1 Jul 2010 18:16:29 +0000 (UTC) [thread overview]
Message-ID: <loom.20100701T195742-266@post.gmane.org> (raw)
Let's create a merge conflict and then partially resolve it:
git init bad-status
cd bad-status/
echo 1 > file
git add file
git commit -a -m1
echo 2 > file
git commit -a -m2
git checkout -b topic HEAD^
echo 3 > file
git commit -a -m3
git merge master
git checkout --ours file
git add file
A 'git status' at this point gives the following output:
# On branch topic
nothing to commit (working directory clean)
Which is wrong, since the merge still needs to be committed.
- Eric
next reply other threads:[~2010-07-01 18:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-01 18:16 Eric Raible [this message]
2010-07-02 0:00 ` Poor status output during conflicted merge Junio C Hamano
2010-07-02 1:51 ` Eric Raible
2010-07-07 0:12 ` Eric Raible
2010-07-07 5:07 ` Elijah Newren
2010-07-07 12:43 ` demerphq
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20100701T195742-266@post.gmane.org \
--to=raible@gmail.com \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).