From: Koen Kooi <koen@dominion.kabel.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: OE.dev roadworks notification
Date: Thu, 21 Feb 2008 10:57:28 +0100 [thread overview]
Message-ID: <fpjhu8$d3l$1@ger.gmane.org> (raw)
In-Reply-To: <c384c5ea0802201437l5a15ddbcu13904422f9bf7aa6@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Leon Woestenberg schreef:
| To what stage is .stable synchronized with current .dev?
People propose revisions from .dev to get backported and 2 core
developers have to ACK them to get applied, and BACKPORTS.txt[1] is
updated with those revisions. That way the stable branch is a 'subset'
of .dev, and we aim to keep 'branch-only' fixes to an absoulute minimum
('zero' is our goal).
| I would like
| to move all my running projects across both branches so that I can
| both
| (1) continue working on them
| (2) test Richard's efforts on .dev
That shouldn't be a problem, if you find something missing, apply the
change locally or propose it for inclusion.
regards,
Koen
[1] e.g.
http://www.openembedded.org:1081/revision/file/4ade39d8fb840c136daf5a450ece76d6b7280dea/BACKPORTS.txt
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFHvUsIMkyGM64RGpERAv4ZAKCZOfIdj6ykpiRh/pOo5bul3yCFOgCfSXCt
gkMYa6UTiNYgEnOoZHiIM8g=
=8o1N
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2008-02-21 9:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-19 11:14 OE.dev roadworks notification Richard Purdie
2008-02-19 11:30 ` Graeme Gregory
2008-02-19 12:07 ` Jeremy Lainé
2008-02-20 22:37 ` Leon Woestenberg
2008-02-21 9:57 ` Koen Kooi [this message]
2008-02-25 21:05 ` Leon Woestenberg
2008-02-20 3:12 ` Junqian Gordon Xu
2008-02-20 3:14 ` Junqian Gordon Xu
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='fpjhu8$d3l$1@ger.gmane.org' \
--to=koen@dominion.kabel.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 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.