From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] e2fsprogs: 1.42.9 -> 1.42.11
Date: Fri, 15 Aug 2014 10:46:50 +0100 [thread overview]
Message-ID: <1408096010.21596.22.camel@ted> (raw)
In-Reply-To: <1408023055.22187.98.camel@ted>
On Thu, 2014-08-14 at 14:30 +0100, Richard Purdie wrote:
> Patches were all merged upstream.
They were but they're not in 1.42.11 :( I'd messed up reading the rather
odd merge history in the upstream git repo. I've put this on ice until
we can upgrade to a version where those patches are available. They
*are* in master branch upstream.
Cheers,
Richard
prev parent reply other threads:[~2014-08-15 9:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-14 13:30 [PATCH] e2fsprogs: 1.42.9 -> 1.42.11 Richard Purdie
2014-08-15 9:46 ` Richard Purdie [this message]
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=1408096010.21596.22.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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