Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Otavio Salvador <otavio@debian.org>
To: openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: openmoko-merges
Date: Thu, 18 Dec 2008 12:23:22 -0200	[thread overview]
Message-ID: <87ocz9sgth.fsf@neumann.lab.ossystems.com.br> (raw)
In-Reply-To: <20081218071901.GB2135@buddha.tw.openmoko.com> (John Lee's message of "Thu\, 18 Dec 2008 15\:19\:01 +0800")

John Lee <john_lee@openmoko.org> writes:

> 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...

Personally I think that OE should have a clear history. There's no
reason  to keep commits like:

 Do foo
 Do something
 Fix foo broken in previous commit
 Really do something
 ...

A clearer and more useful history would be:

 Do something
 Do foo
 ...

And it should not be hard to merge it back into OpenMoko tree since
the 3-way merge will detect the same changes and should reduce the
conflicts a lot.

Anyway, I personally prefer to have clearer history then keep the
whole list of commits there. Others?

-- 
        O T A V I O    S A L V A D O R
---------------------------------------------
 E-mail: otavio@debian.org      UIN: 5906116
 GNU/Linux User: 239058     GPG ID: 49A5F855
 Home Page: http://otavio.ossystems.com.br
---------------------------------------------
"Microsoft sells you Windows ... Linux gives
 you the whole house."



  parent reply	other threads:[~2008-12-18 14:32 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 ` Otavio Salvador [this message]
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           ` 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=87ocz9sgth.fsf@neumann.lab.ossystems.com.br \
    --to=otavio@debian.org \
    --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