From: Benny Halevy <bhalevy@panasas.com>
To: git@vger.kernel.org
Subject: new file missing after resolving rebase merge conflict
Date: Sun, 24 Aug 2008 20:20:50 +0300 [thread overview]
Message-ID: <48B19872.9070707@panasas.com> (raw)
with git version 1.6.0
When rebasing a branch onto another
(command was git rebase --onto newbase newbase.orig branch)
I've hit a merge conflict in one of the patches that
among other things, adds some new files to the tree.
After resolving the conflict and running git add on the
resolved files I ran git rebase --continue and in a later
patch, when trying to compile I noticed that one of the files
that the former patch was supposed to add is missing from the
tree and from the index.
I'm not sure it's relevant, yet this file is the last hunk in
the patch.
Anyhow, the file still appears with git show of the rebased
patch:
$ git show 39fe203
...
diff --git a/include/linux/pnfs_xdr.h b/include/linux/pnfs_xdr.h
new file mode 100644
index 0000000..1f811c5
--- /dev/null
+++ b/include/linux/pnfs_xdr.h
@@ -0,0 +1,137 @@
but it doesn't appear to exist in the index:
$ git checkout include/linux/pnfs_xdr.h
error: pathspec 'include/linux/pnfs_xdr.h' did not match any file(s) known to git.
only after explicitly re-checking it out from the former patch:
$ git checkout 39fe203 -- include/linux/pnfs_xdr.h
it comes to existence.
Benny
reply other threads:[~2008-08-24 17:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=48B19872.9070707@panasas.com \
--to=bhalevy@panasas.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.