From: Sven Verdoolaege <skimo@kotnet.org>
To: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: rebase problems
Date: Mon, 28 Nov 2005 15:58:14 +0100 [thread overview]
Message-ID: <20051128145814.GW8383MdfPADPa@greensroom.kotnet.org> (raw)
Recently, rebasing has stopped working for me.
Here is an example:
bash-3.00$ git-show-branch origin HEAD
! [origin] fix in which we remove the definition of index statements that are *not* used in the control vector
! [HEAD] propagate LinearizationType typo fix.
--
+ [HEAD] propagate LinearizationType typo fix.
+ [HEAD^] LinearizationType: typo
+ [HEAD~2] espam::DecomposeChannels: actually decompose the channel if valid.
+ [HEAD~3] DecomposeChannels: split channel and check whether result is a pair of fifos.
+ [HEAD~4] Use proper class for LinearizationType.
+ [HEAD~5] espam/../DecomposeChannels: partial implementation.
+ [HEAD~6] espam: add flag for channel decomposition.
+ [origin] fix in which we remove the definition of index statements that are *not* used in the control vector
++ [HEAD~7] espam/../IndexVector::toString: include contents of IndexVector.
bash-3.00$ git rebase origin
Applying 'espam::DecomposeChannels: actually decompose the channel if valid.'
error: pa/espam/operations/transformations/DecomposeChannels.java: does not exist in index
Using index info to reconstruct a base tree...
Falling back to patching base and 3-way merge...
Trying simple merge.
Simple merge failed, trying Automatic merge.
ERROR: pa/espam/operations/transformations/DecomposeChannels.java: Not handling case 09322db769adbc03bfd4f3ac2720c6d1db5a85b1 -> -> 32da8b1de4205c4adb0da50648a0a00d60b67582
fatal: merge program failed
Failed to merge in the changes.
Patch failed at 0007.
0001-espam-add-flag-for-channel-decomposition.txt
I'm not sure what rebase is doing here, but the only change in origin
modified a file untouched by the changes in HEAD, so there shouldn't
be any conflict whatsoever.
Apparently it's trying to apply the change in HEAD~2 without having
applied the earlier changes (which and the file named above).
skimo
PS: I'll try and look into the gitk thing this evening.
next reply other threads:[~2005-11-28 14:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-28 14:58 Sven Verdoolaege [this message]
2005-11-28 20:19 ` rebase problems Junio C Hamano
2005-11-28 20:24 ` Sven Verdoolaege
2005-11-28 21:02 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2010-11-08 18:19 Rebase problems Maaartin
2010-11-08 18:33 ` Wincent Colaiuta
2010-11-08 19:59 ` Maaartin-1
2010-11-12 0:07 ` Maaartin
2010-11-08 19:30 ` Andreas Schwab
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=20051128145814.GW8383MdfPADPa@greensroom.kotnet.org \
--to=skimo@kotnet.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=skimo@liacs.nl \
/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).