From: Gene Czarcinski <gene@czarc.net>
To: Git <git@vger.kernel.org>
Subject: Bug, feature, or pilot error: format-patch
Date: Mon, 28 Jan 2013 12:03:56 -0500 [thread overview]
Message-ID: <5106AF7C.1010502@czarc.net> (raw)
I am not on the mailing list so please CC me. I am running git 1.8.1 on
Fedora 18.
I aam having what appears to be a problem. Here is the sequence which
generally describes what I did and what happened:
git checkout -b test1 master
git am 0001-simple-1.patch
git checkout -b test2 master
git am 0001-simple-2.patch ### this is known to conflict
with 0001-simple-1.patch
git checkout test1
git merge test2
[here git-merge detects a conflict]
git mergetool ###to resolve the conflict
[conflict resolved]
git commit -a -s
git log
[shows two commits -- one for simple-2 and one for the merge]
git format-patch master..HEAD
[two patch files created: 0001-simple-1.patch and 0002-simple-2.patch]
[0002-simple-2.patch and 0001-simple-2.patch are exactly equal and do
not reflect the resolved conflict]
If you do git-diff between <commit-patch-1> and HEAD, you get something
different that you got from format-patch.
1. Bug ... format-patch is broken
2. Feature ... that is the way it works
3. Pilot error ... ??
I can create a good version of patch-2 manually but should I have to?
Color me foolish but I assumed I could do git-format-patch in one branch
and then use git-am to recreate that branch elsewhere.
Gene
next reply other threads:[~2013-01-28 17:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-28 17:03 Gene Czarcinski [this message]
2013-01-30 14:41 ` Bug, feature, or pilot error: format-patch Gene Czarcinski
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=5106AF7C.1010502@czarc.net \
--to=gene@czarc.net \
--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).