From: "J.V." <jvsrvcs@gmail.com>
To: git@vger.kernel.org
Subject: merge help
Date: Tue, 26 Mar 2013 16:07:23 -0600 [thread overview]
Message-ID: <51521C1B.3080307@gmail.com> (raw)
I have a branch for which I have made 0 (nada) changes. I did the
following:
$git pull --rebase --no-stat -v --progress origin mybranch
I get the following
U java/Profile.java
Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm <file>'
as appropriate to mark resolution, or use 'git commit -a'.
---------- (there is no local master branch), because of the conflict
I was put on (no branch)
* (no branch)
branch1
dev
tmpWork
Question 1)
Why did I get a merge conflict if I have not changed any files?
Question 2)
What is the command to show the difference between the files? (is there
a visual tool that would let me merge)?
Question 3)
What is the command I would type to "accept theirs" and overwrite my local?
After this would I need to $git add & commit & push the file?
If someone could guide me through this initial process, (what is best
recommended it would be most helpful).
thanks
J.V.
next reply other threads:[~2013-03-26 22:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 22:07 J.V. [this message]
2013-03-27 14:10 ` merge help Magnus Bäck
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=51521C1B.3080307@gmail.com \
--to=jvsrvcs@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.
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).