public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: green <greenfreedom10@gmail.com>
To: Linux-OMAP List <linux-omap@vger.kernel.org>
Subject: Re: using git with linux-omap
Date: Sat, 24 Jan 2009 15:20:08 -0700	[thread overview]
Message-ID: <20090124222008.GA6457@swansys> (raw)
In-Reply-To: <20081225195450.GF10240@frodo>

[-- Attachment #1: Type: text/plain, Size: 1280 bytes --]

On Thu, 2008-12-25, 360, Felipe Balbi wrote:
> On Wed, Dec 24, 2008 at 06:46:31PM -0600, green wrote:
> > 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.
> 
> maybe I got the parameters wrong. git help rebase will have the correct
> answer.

Hey, I got it to work:
git rebase --onto v2.6.27-omap1 master <my_branch>

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

      parent reply	other threads:[~2009-01-24 22:20 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
2008-12-25 19:55     ` Felipe Balbi
2009-01-08 17:02       ` green
2009-01-24 22:20       ` green [this message]

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=20090124222008.GA6457@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