From: Stephen Kelly <steveire@gmail.com>
To: git@vger.kernel.org
Subject: No way to resolve git am conflicts.
Date: Sat, 08 Jan 2011 14:11:54 +0100 [thread overview]
Message-ID: <ig9nqq$4ib$1@dough.gmane.org> (raw)
kde-devel@bishop:~/dev/src/git{master}$ curl -o the.patch
http://download.gmane.org/gmane.comp.version-control.git/164809/164810 &&
git am the.patch
% Total % Received % Xferd Average Speed Time Time Time
Current
Dload Upload Total Spent Left
Speed
100 10438 0 10438 0 0 12046 0 --:--:-- --:--:-- --:--:--
13451
Applying: Introduce new configuation option to override committer
information
error: patch failed: builtin/commit.c:1352
error: builtin/commit.c: patch does not apply
Patch failed at 0001 Introduce new configuation option to override committer
information
When you have resolved this problem run "git am --resolved".
If you would prefer to skip this patch, instead run "git am --skip".
To restore the original branch and stop patching run "git am --abort".
Qt( 4.7 ) KDE ( 4.6 )
kde-devel@bishop:~/dev/src/git{master}$ git diff
Qt( 4.7 ) KDE ( 4.6 )
kde-devel@bishop:~/dev/src/git{master}$ git status
# On branch master
# Untracked files:
# (use "git add <file>..." to include in what will be committed)
#
# p.patch
# the.patch
nothing added to commit but untracked files present (use "git add" to track)
Qt( 4.7 ) KDE ( 4.6 )
kde-devel@bishop:~/dev/src/git{master}$
As git status doesn't tell me what the conflict is, I can't resolve it.
next reply other threads:[~2011-01-08 13:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-08 13:11 Stephen Kelly [this message]
2011-01-08 16:36 ` No way to resolve git am conflicts Jonathan Nieder
2011-01-08 19:21 ` Stephen Kelly
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='ig9nqq$4ib$1@dough.gmane.org' \
--to=steveire@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).