From: Martin Jansa <martin.jansa@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Minutes: Yocto Project 1.4 M4 release readiness discussion
Date: Sat, 2 Mar 2013 00:32:55 +0100 [thread overview]
Message-ID: <20130301233255.GW3279@jama> (raw)
In-Reply-To: <CAJTo0LZuw_va=yjLyRZ=mWCNMVDvwe0_fYB23ckbvuZ=irgqaA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1149 bytes --]
On Fri, Mar 01, 2013 at 11:08:30PM +0000, Burton, Ross wrote:
> On 1 March 2013 21:53, Martin Jansa <martin.jansa@gmail.com> wrote:
> > I think it would be good to finish discussion in thread
> > [OE-core] RFE: make the init manager an image feature (again)
> > and resolve systemd situation asap, otherwise we're risking
> > meta-openembedded release or quality of such release.
>
> I'm working on a series that implements roughly what I proposed
> (systemd and sysvinit features not mutually exclusive, but no separate
> -sysv or -systemd packages) and hope to have it on the list next week
> - this week has been slow going as we've had a family cold do the
> rounds.
Can you answer this
http://lists.linuxtogo.org/pipermail/openembedded-core/2013-February/036223.html
and how this solution helps with upgrade paths?
> Any contributions of coding are always welcome, obviously.
Coding was contributed to meta-systemd which was working fine for both
use-cases. Maybe explaining hidden benefits of not splitted packages
would motivate some people..
Cheers,
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2013-03-01 23:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-01 20:01 Minutes: Yocto Project 1.4 M4 release readiness discussion Liu, Song
2013-03-01 21:53 ` Martin Jansa
2013-03-01 23:08 ` Burton, Ross
2013-03-01 23:32 ` Martin Jansa [this message]
2013-03-01 23:56 ` Burton, Ross
2013-03-02 0:14 ` Martin Jansa
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=20130301233255.GW3279@jama \
--to=martin.jansa@gmail.com \
--cc=ross.burton@intel.com \
--cc=yocto@yoctoproject.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.