From: Len Brown <len.brown@intel.com>
To: Junio C Hamano <junkio@cox.net>
Cc: Linus Torvalds <torvalds@osdl.org>, git@vger.kernel.org
Subject: Re: Automatic merge failed, fix up by hand
Date: Tue, 23 Aug 2005 20:31:09 -0400 [thread overview]
Message-ID: <1124843469.14730.13.camel@toshiba> (raw)
In-Reply-To: <7vzmr8mci2.fsf@assigned-by-dhcp.cox.net>
On Tue, 2005-08-23 at 19:58 -0400, Junio C Hamano wrote:
> Len Brown <len.brown@intel.com> writes:
>
> >> I could get to 81065e2f415af6... commit (Linus tip at this
> >> moment), so if you can tell me where to snarf the other commit
> >> (702c7e76....) that would help me diagnose the problem a lot.
> >
> > rsync://rsync.kernel.org/pub/scm/linux/kernel/git/lenb/to-akpm.git
>
> Thanks.
>
> I think merge-base, even though we attempted to fix it recently,
> is still confused and that is one of the reasons why you are
> getting this.
>
> prompt$ git-rev-parse origin test-lenb-merge
> 81065e2f415af6c028eac13f481fb9e60a0b487b
> 702c7e7626deeabb057b6f529167b65ec2eefbdb
> prompt$ git-merge-base origin test-lenb-merge
> 30e332f3307e9f7718490a706e5ce99f0d3a7b26
> prompt$ git show-branch origin test-lenb-merge
> ! [origin] zd1201 kmalloc size fix
> * [test-lenb-merge] [ACPI] fix ia64 build issues resulting from
> L...
> --
> + [origin] zd1201 kmalloc size fix
> + [origin~1] md: make sure resync gets started when array starts.
> + [origin~2] preempt race in getppid
> + [origin~3] Merge master.kernel.org:/pub/scm/linux/kernel/git/da
> -- >8 -- snip -- >8 --
> + Merge ../to-linus-stable/
> ++ [ACPI] re-enable platform-specific hotkey drivers by default
> + ARM: 2851/1: Fix NWFPE extended precision exception handling
> ++ [origin~34] intelfb/fbdev: Save info->flags in a local variable
> prompt$ git-rev-parse origin~34
> 3edea4833a1efcd43e1dff082bc8001fdfe74b34
>
> Notice that show-branch, which walks the commit ancestry chain
> pretty much the same way merge-base does, notices and stops at
> origin~34 (that's 34th generation first parent commit from Linus
> tip) that is the common commit between the two heads being
> merged? And that commit, 3edea48... is different from what
> merge-base is reporting.
>
> If I maually run merge-cache using origin~34 as the merge base,
> only the following two files needs to result in non-simple merge:
>
> Documentation/acpi-hotkey.txt
> drivers/acpi/osl.c
>
> Do these two files match your expectation?
No, I don't think so.
Unless I missed something, to-akpm should be a proper super-set
of from-linus, so I wouldn't expect a merge on these two.
> I'll take a look at merge-base.c next, but just in case I CC:ed
> this to Linus, who is more familiar with that code.
thanks,
-Len
next prev parent reply other threads:[~2005-08-24 0:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-23 21:12 Automatic merge failed, fix up by hand Len Brown
2005-08-23 22:06 ` Junio C Hamano
2005-08-23 22:31 ` Len Brown
2005-08-23 23:58 ` Junio C Hamano
2005-08-24 0:29 ` Junio C Hamano
2005-08-24 1:07 ` Junio C Hamano
2005-08-24 1:28 ` Linus Torvalds
2005-08-24 3:52 ` Junio C Hamano
2005-08-24 2:25 ` Len Brown
2005-08-24 3:11 ` Daniel Barkalow
2005-08-24 0:31 ` Len Brown [this message]
2005-08-24 0:48 ` Linus Torvalds
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=1124843469.14730.13.camel@toshiba \
--to=len.brown@intel.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=torvalds@osdl.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).