From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-devel@lists.openembedded.org
Cc: Koen Kooi <koen@dominion.thruhere.net>
Subject: Re: [meta-systemd][PATCH V2 1/7] systemd: Upgrade to 187
Date: Thu, 02 Aug 2012 09:11:10 +0100 [thread overview]
Message-ID: <671950423.c3foblMkXu@helios> (raw)
In-Reply-To: <BCFACC99-6EAF-4C57-B8E2-18DA0E62BAB3@gmail.com>
On Wednesday 01 August 2012 15:56:34 Khem Raj wrote:
> On Aug 1, 2012, at 8:11 AM, Koen Kooi <koen@dominion.thruhere.net> wrote:
> >> Along with upgrade use the release tarballs instead of git
> >
> > For an update we need to pull in some patches from master, so a git recipe
> > is still the preferred way.
>
> OK, you know more about it then me but do you know how many those will be ?
> in other words does systemd releases mean much for stability yet or still
> its a project moving at so fast pace ?
>
> I see that releases are rolled out almost every month, that sort of could
> mean either way, we wait until the next release or just take from a commit
> upstream
>
> I feel like staying with a release+patches could be one way if we are not
> importing pathes too often. but I don't know how often that would be. For
> the testing I did release worked well for those platforms x86, ppc and arm
One might suggest, if stable releases are working and you want to live on the
bleeding edge in your distro, you can easily do so there...
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-08-02 8:22 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 18:56 [meta-systemd][PATCH V2 1/7] systemd: Upgrade to 187 Khem Raj
2012-07-31 18:56 ` [meta-systemd][PATCH V2 2/7] busybox: stopping systemd-kmsg-syslogd is not needed Khem Raj
2012-07-31 18:56 ` [meta-systemd][PATCH V2 3/7] busybox-syslog.service.in: Create alias for syslog.service Khem Raj
2012-07-31 18:56 ` [meta-systemd][PATCH V2 4/7] systemd: Use cross cpp Khem Raj
2012-07-31 18:56 ` [meta-oe][PATCH V2 5/7] testlab.bbclass: Delete Khem Raj
2012-07-31 18:56 ` [meta-oe][PATCH V2 6/7] blacklist.bbclass: Move to meta-angstrom Khem Raj
2012-07-31 19:07 ` Koen Kooi
2012-07-31 19:24 ` Chris Larson
2012-07-31 19:43 ` Martin Jansa
2012-07-31 20:46 ` Khem Raj
2012-08-04 20:36 ` Koen Kooi
2012-08-04 20:47 ` Khem Raj
2012-08-04 21:56 ` Philip Balister
2012-08-05 11:41 ` Koen Kooi
2012-08-05 19:44 ` Khem Raj
2012-08-05 21:37 ` Chris Larson
2012-08-05 22:06 ` Khem Raj
2012-08-06 7:43 ` Koen Kooi
2012-08-07 2:38 ` Khem Raj
2012-07-31 18:56 ` [meta-oe][PATCH V2 7/7] kernel.bbclass: Rename to machine_kernel_pr.bbclass which provides added functionality Khem Raj
2012-08-01 17:38 ` Otavio Salvador
2012-08-01 22:31 ` Khem Raj
2012-08-01 15:11 ` [meta-systemd][PATCH V2 1/7] systemd: Upgrade to 187 Koen Kooi
2012-08-01 22:56 ` Khem Raj
2012-08-02 8:11 ` Paul Eggleton [this message]
2012-08-03 10:32 ` Khem Raj
2012-08-03 12:38 ` Koen Kooi
2012-08-03 14:41 ` Khem Raj
2012-08-03 15:36 ` Koen Kooi
2012-08-03 18:39 ` Khem Raj
2012-08-03 18:42 ` Martin Jansa
2012-08-03 19:08 ` Koen Kooi
2012-08-04 20:10 ` Khem Raj
2012-08-04 20:35 ` Koen Kooi
2012-08-04 20:50 ` Khem Raj
2012-08-05 11:42 ` Koen Kooi
2012-08-05 11:53 ` Philip Balister
2012-08-05 19:40 ` Khem Raj
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=671950423.c3foblMkXu@helios \
--to=paul.eggleton@linux.intel.com \
--cc=koen@dominion.thruhere.net \
--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.