From: Saul Wold <sgw@linux.intel.com>
To: Marko Lindqvist <cazfi74@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [CONSOLIDATED PULL (V2) 00/35] Updates, Multilib Patches and other fixes
Date: Sat, 05 Jan 2013 20:29:47 -0800 [thread overview]
Message-ID: <50E8FDBB.5080500@linux.intel.com> (raw)
In-Reply-To: <CAF6bG8ed60RO2bBTPFhKQiG+3xis6-H9icmLDWtwHCO9NAyadw@mail.gmail.com>
On 01/04/2013 10:52 PM, Marko Lindqvist wrote:
> On 5 January 2013 08:22, Saul Wold <sgw@linux.intel.com> wrote:
>>
>> Saul Wold (3):
>> glib-2.0: Update to 2.35.3
>
> Is there some specific need for bleeding edge (unstable development snapshot)?
>
I was updating glib-networking and it required glib 2.35.3, I had not
checked (my bad that it was unstable). Even after a number of years, I
loose track sometimes of what's stable vs unstable (odd vs .99 vs ??)
We can drop both the glib and glib-networking patches.
Sau!
>
>
> - ML
>
next prev parent reply other threads:[~2013-01-06 4:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-05 6:22 [CONSOLIDATED PULL (V2) 00/35] Updates, Multilib Patches and other fixes Saul Wold
2013-01-05 6:52 ` Marko Lindqvist
2013-01-06 4:29 ` Saul Wold [this message]
2013-01-06 20:28 ` Marko Lindqvist
2013-01-09 7:46 ` Marko Lindqvist
2013-01-09 9:13 ` Martin Jansa
2013-01-09 9:33 ` Marko Lindqvist
2013-01-09 9:42 ` Ross Burton
2013-01-09 10:00 ` Marko Lindqvist
2013-01-09 10:29 ` Martin Jansa
2013-01-09 10:42 ` Marko Lindqvist
2013-01-05 23:36 ` Marko Lindqvist
2013-01-07 11:10 ` Richard Purdie
2013-01-07 12:31 ` Laurentiu Palcu
2013-01-07 12:38 ` Marko Lindqvist
2013-01-07 12:41 ` Laurentiu Palcu
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=50E8FDBB.5080500@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=cazfi74@gmail.com \
--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