From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Anders Darander <anders@chargestorm.se>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: RFC: systemd version - release or git?
Date: Wed, 19 Feb 2014 15:47:12 +0000 [thread overview]
Message-ID: <1392824832.14081.274.camel@ted> (raw)
In-Reply-To: <20140219113705.GA9147@ad.chargestorm.se>
On Wed, 2014-02-19 at 12:37 +0100, Anders Darander wrote:
> * Martin Jansa <martin.jansa@gmail.com> [140219 12:26]:
> > On Wed, Feb 19, 2014 at 10:54:50AM +0000, Richard Purdie wrote:
> > > Any objections to defaulting to a git version?
>
> > I think we can wait few more days for new release:
> > https://www.mail-archive.com/systemd-devel@lists.freedesktop.org/msg16738.html
>
> I was just about to reply with the same e-mail link...
I asked about this a few days ago and scanned the archives and didn't
find it. Typically, they sent it out after I did that :)
> > but otherwise I don't have strong objections for switching to git
> > version temporary (if it really makes QA test results better).
>
> Otherwise, I don't have any strong feelings against a git version. Not
> as long as it works as it should.
>
> One objection might be that it's easier for someone to update it to a
> strange version in between the regular releases. As long as we try to
> avoid making a release where systemd is too far of from a regular
> release, that shouldn't be any issue, though.
I agree its worth waiting for the release if it really is than imminent.
I'd previously not been able to find a commitment or schedule.
It might be useful to have a git based recipe anyway for
debugging/testing...
Cheers,
Richard
next prev parent reply other threads:[~2014-02-19 15:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-19 10:54 RFC: systemd version - release or git? Richard Purdie
2014-02-19 11:26 ` Martin Jansa
2014-02-19 11:37 ` Anders Darander
2014-02-19 15:47 ` Richard Purdie [this message]
2014-02-20 6:52 ` Koen Kooi
2014-02-19 11:32 ` 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=1392824832.14081.274.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=anders@chargestorm.se \
--cc=openembedded-core@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