From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Andreas M?ller <schnitzeltony@gmail.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 1/2] libnotify: upgrade 0.7.8 -> 0.7.9 / port to meson
Date: Thu, 26 Mar 2020 10:02:37 +0000 [thread overview]
Message-ID: <3ac793ad1e480d3af9c599bdce6e21a02a33162d.camel@linuxfoundation.org> (raw)
In-Reply-To: <CALbNGRQ-4wLXC-fttpLc6ixJYxWb0HHGgsDQr+x8RhvxLGOgpw@mail.gmail.com>
On Thu, 2020-03-26 at 09:13 +0100, Andreas M?ller wrote:
> On Thu, Mar 19, 2020 at 2:12 AM Andreas Müller <
> schnitzeltony@gmail.com> wrote:
> > From [1]:
> > New in 0.7.9
> > ============
> > * Fixed linking in darwin [Iain, Marco; !5]
> > * Added man page for notify-send [Jan; !6]
> > * Dropped autotools [Jan; !11]
> >
> > [1]
> > http://ftp.gnome.org/pub/gnome/sources/libnotify/0.7/libnotify-0.7.9.news
> >
> > Signed-off-by: Andreas Müller <schnitzeltony@gmail.com>
> >
> >
> Ping?
We're at feature freeze and stabilisation for 3.1. I've already taken a
number of things I probably shouldn't at this stage but changing
software over to meson poses far too much risk at this point in the
release so this cannot go in, sorry.
Cheers,
Richard
next prev parent reply other threads:[~2020-03-26 10:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-19 1:12 [PATCH 1/2] libnotify: upgrade 0.7.8 -> 0.7.9 / port to meson Andreas Müller
2020-03-19 1:12 ` [PATCH 2/2] libsecret: upgrade 0.20.1 -> 0.20.2 " Andreas Müller
2020-03-26 8:13 ` Andreas M?ller
2020-03-26 8:13 ` [PATCH 1/2] libnotify: upgrade 0.7.8 -> 0.7.9 " Andreas M?ller
2020-03-26 10:02 ` Richard Purdie [this message]
2020-03-26 11:04 ` [OE-core] " Andreas M?ller
-- strict thread matches above, loose matches on Subject: below --
2020-04-30 21:42 Andreas M?ller
2020-05-03 8:22 ` [OE-core] " Richard Purdie
2020-05-03 19:22 ` Andreas M?ller
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=3ac793ad1e480d3af9c599bdce6e21a02a33162d.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=schnitzeltony@gmail.com \
/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