From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] Make some big changes right after next stable
Date: Wed, 03 Mar 2010 19:16:50 +0100 [thread overview]
Message-ID: <hmm92i$r30$1@dough.gmane.org> (raw)
In-Reply-To: <20100303180851.GC2493@xora-desktop.xora.org.uk>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 03-03-10 19:08, Graeme Gregory wrote:
> On Wed, Mar 03, 2010 at 10:33:07AM -0700, Tom Rini wrote:
>> Note that I'm not talking about "small" things like removing legacy
>> staging stuff (which is good!) I'm talking about things with the
>> potential to leave stuff non-building until stumbled upon. Hence the
>> idea we do merge this into dev shortly after the next stable.
>>
> I think you are approaching things backwards.
>
> Develop this to the point of working enough other people can start to test it
> in a feature branch.
>
> Tag org.openembedded.dev then merge this work into .dev
>
> Anyone in the future can use the tag to get back to a "stable" point.
That's what I wanted to say, but Graeme put it way better :)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFLjqeSMkyGM64RGpERAmvHAJ4q4v5Ig/lnD2UaW7ffx3R6T1AFdwCeIJcI
bJ9NE/LbnxvZfMzuuvjqAv8=
=rTPS
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-03-03 18:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-03 16:30 [RFC] Make some big changes right after next stable Tom Rini
2010-03-03 17:20 ` Koen Kooi
2010-03-03 17:33 ` Tom Rini
2010-03-03 18:08 ` Graeme Gregory
2010-03-03 18:16 ` Koen Kooi [this message]
2010-03-03 18:18 ` Tom Rini
2010-03-03 18:18 ` Michael 'Mickey' Lauer
2010-03-04 10:18 ` Richard Purdie
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='hmm92i$r30$1@dough.gmane.org' \
--to=k.kooi@student.utwente.nl \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.