Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Graeme Gregory <dp@xora.org.uk>
To: openembedded-devel@lists.openembedded.org
Subject: Re: openmoko-merges
Date: Fri, 19 Dec 2008 10:48:48 +0000	[thread overview]
Message-ID: <494B7C10.8090407@xora.org.uk> (raw)
In-Reply-To: <20081219053858.GQ2135@buddha.tw.openmoko.com>

John Lee wrote:
> I'll keep working on the fastboot branch (need the help of original
> author on this one.  since this will become general changes, it's not
> going to be easy), and reorganize the om-merge branch a bit.  Is this
> the first time of such a big merge ?  I think Graeme and I both did
> some merge back before, but this one seems to be bigger...
>
>   
I used to use a process similar to what koen suggested where I would
only merge back into OE the final changes to a .bb not all the
mistakes/fuckups/typos that got us to that result. Then evaluate each
change on its own to judge its level of controversy.

Graeme




  reply	other threads:[~2008-12-19 10:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-18  7:19 openmoko-merges John Lee
2008-12-18  9:02 ` openmoko-merges Koen Kooi
2008-12-18 10:11   ` openmoko-merges John Lee
2008-12-18 10:39     ` openmoko-merges Koen Kooi
2008-12-18 14:23 ` openmoko-merges Otavio Salvador
2008-12-18 15:05 ` openmoko-merges John Lee
2008-12-18 15:24   ` openmoko-merges Koen Kooi
2008-12-18 16:35     ` openmoko-merges John Lee
2008-12-18 16:54     ` openmoko-merges Phil Blundell
2008-12-18 18:05       ` openmoko-merges Koen Kooi
2008-12-19  5:38         ` openmoko-merges John Lee
2008-12-19 10:48           ` Graeme Gregory [this message]
2008-12-19 19:46             ` openmoko-merges Ricardo Salveti de Araujo
2008-12-19 20:03               ` openmoko-merges Tom Rini
2008-12-19 23:37                 ` openmoko-merges Koen Kooi

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=494B7C10.8090407@xora.org.uk \
    --to=dp@xora.org.uk \
    --cc=openembedded-devel@lists.openembedded.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