Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: openmoko-merges
Date: Thu, 18 Dec 2008 16:24:04 +0100	[thread overview]
Message-ID: <gidpuk$29d$1@ger.gmane.org> (raw)
In-Reply-To: <20081218150517.GI2135@buddha.tw.openmoko.com>

On 18-12-08 16:05, John Lee wrote:
> Okay, here is what I will do:
>
> 1) commit zero controversial part into oe.dev first.

You don't know if it's controversial or not without it being reviewed. 
So no, don't commit stuff.

> 2) put fastboot related stuffs into another branch for review

Make another branch for the stuff you thing is non-controversial so we 
can review that as well.

> 3) rebase -i the rest to create a clean history, force update the
> openmoko-merges branch, then ask for review again.

Try to keep every branch below approx 30 commits, otherwise it becomes 
to cumbersome to review.

regards,

Koen

>
>
> Regards,
> John
>
>
>
>
> On Thu, Dec 18, 2008 at 03:19:01PM +0800, John Lee wrote:
>> Hi,
>>
>> Please review john_lee/openmoko-merges.  I started from
>> holger/openmoko-merges then rebased it to oe.dev.
>>
>> The general principle is:
>>
>> 1) Minimal impact: most of the big changes apply to om distro only.
>> My thought is we merge this first, then apply to the general.
>>
>> 2) Keep history: I did it the hard way by cherry-picking one by one
>> since the history is different after the mtn->git switch.  Most of the
>> commit messages are kept, but that creates a lot of commits to review.
>>
>> 3) PKG_TAGS, qtopia, toolchain, om-utils and opkg stuffs are left out
>> for later merge.
>>
>> Not sure how long it's going to take.  My plan is to merge it this
>> Monday if it's okay...
>>
>>
>> Regards,
>> John
>>
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel





  reply	other threads:[~2008-12-18 15:28 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   ` Koen Kooi [this message]
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           ` openmoko-merges Graeme Gregory
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='gidpuk$29d$1@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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