From: green <greenfreedom10@gmail.com>
To: Linux-OMAP List <linux-omap@vger.kernel.org>
Subject: Re: using git with linux-omap
Date: Wed, 24 Dec 2008 18:46:31 -0600 [thread overview]
Message-ID: <20081225004631.GH4080@swansys> (raw)
In-Reply-To: <20081224041903.GD10240@frodo>
[-- Attachment #1: Type: text/plain, Size: 3404 bytes --]
On Wed, 2008.12.24, 359, Felipe Balbi wrote:
> On Tue, Dec 23, 2008 at 09:24:19PM -0600, green wrote:
> > I have cloned linux-omap-2.6 and created a local branch. In the local branch I
> > have made one very simple commit with a single line change to Makefile for use
> > when cross-compiling (arm-linux-gnueabi-). I would like to be able to rebase
> > that branch (just the 1 commit) onto any commit in the master branch so that I
> > can test N810 builds using git-bisect without modifying the Makefile every
> > time. I can easily move the branch forward to the latest commit with 'git
> > rebase master' (with the local branch active) but something like 'git rebase
> > v2.6.27-omap1' returns merge errors. Of course that 1 commit will apply easily
> > to that specific tree.
>
> hmmm, something like git rebase --onto HEAD v2.6.27-omap1 <your_branch>
> should work.
I got a bunch of merge conflicts this way.
$ git rebase --onto HEAD v2.6.27-omap1 custom
First, rewinding head to replay your work on top of it...
Applying x86, ptrace: PEBS support
error: patch failed: arch/x86/Kconfig.cpu:415
error: arch/x86/Kconfig.cpu: patch does not apply
error: patch failed: arch/x86/kernel/cpu/intel.c:222
error: arch/x86/kernel/cpu/intel.c: patch does not apply
error: patch failed: arch/x86/kernel/ds.c:2
error: arch/x86/kernel/ds.c: patch does not apply
error: patch failed: arch/x86/kernel/process_32.c:316
error: arch/x86/kernel/process_32.c: patch does not apply
error: patch failed: arch/x86/kernel/process_64.c:267
error: arch/x86/kernel/process_64.c: patch does not apply
error: patch failed: arch/x86/kernel/ptrace.c:554
error: arch/x86/kernel/ptrace.c: patch does not apply
error: arch/x86/kernel/setup_64.c: does not exist in index
error: include/asm-x86/ds.h: does not exist in index
error: include/asm-x86/processor.h: does not exist in index
error: include/asm-x86/ptrace-abi.h: does not exist in index
error: include/asm-x86/ptrace.h: does not exist in index
Using index info to reconstruct a base tree...
Falling back to patching base and 3-way merge...
Auto-merged arch/x86/Kconfig.cpu
CONFLICT (content): Merge conflict in arch/x86/Kconfig.cpu
Auto-merged arch/x86/kernel/cpu/intel.c
CONFLICT (content): Merge conflict in arch/x86/kernel/cpu/intel.c
Auto-merged arch/x86/kernel/ds.c
CONFLICT (content): Merge conflict in arch/x86/kernel/ds.c
Auto-merged arch/x86/kernel/process_32.c
CONFLICT (content): Merge conflict in arch/x86/kernel/process_32.c
Auto-merged arch/x86/kernel/process_64.c
CONFLICT (content): Merge conflict in arch/x86/kernel/process_64.c
Auto-merged arch/x86/kernel/ptrace.c
CONFLICT (content): Merge conflict in arch/x86/kernel/ptrace.c
CONFLICT (delete/modify): arch/x86/kernel/setup_64.c deleted in HEAD and
modified in x86, ptrace: PEBS support. Version x86, ptrace: PEBS support of
arch/x86/kernel/setup_64.c left in tree.
CONFLICT (delete/modify): include/asm-x86/ds.h deleted in HEAD and modified in
x86, ptrace: PEBS support. Version x86, ptrace: PEBS support of
include/asm-x86/ds.h left in tree.
Failed to merge in the changes.
Patch failed at 0001.
When you have resolved this problem run "git rebase --continue".
If you would prefer to skip this patch, instead run "git rebase --skip".
To restore the original branch and stop rebasing run "git rebase --abort".
Thanks.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-12-25 0:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-24 3:24 using git with linux-omap green
2008-12-24 4:19 ` Felipe Balbi
2008-12-25 0:46 ` green [this message]
2008-12-25 19:55 ` Felipe Balbi
2009-01-08 17:02 ` green
2009-01-24 22:20 ` green
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=20081225004631.GH4080@swansys \
--to=greenfreedom10@gmail.com \
--cc=linux-omap@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