From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Saul Wold <sgw@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/6] Updates and bug fixes
Date: Wed, 24 Dec 2014 00:27:16 +0000 [thread overview]
Message-ID: <1419380836.6428.7.camel@linuxfoundation.org> (raw)
In-Reply-To: <5499F33E.2070306@linux.intel.com>
On Tue, 2014-12-23 at 14:57 -0800, Saul Wold wrote:
> ping!
Three went in, the other three did not since when Ross and I tried
fetching them, the files existed and there was no need to convert to
git. Please retest.
Cheers,
Richard
next prev parent reply other threads:[~2014-12-24 0:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 5:55 [PATCH 0/6] Updates and bug fixes Saul Wold
2014-12-10 5:55 ` [PATCH 1/6][v4] procps: Upgrade to 3.3.10 Saul Wold
2014-12-10 5:55 ` [PATCH 2/6] babeltrace: Update to 1.2.4 Saul Wold
2014-12-10 5:55 ` [PATCH 3/6] npth: npth needs pthread in some cases Saul Wold
2014-12-10 5:55 ` [PATCH 4/6] libdaemon: Convert to git Saul Wold
2014-12-10 5:55 ` [PATCH 5/6] libnss-mdns: " Saul Wold
2014-12-10 5:55 ` [PATCH 6/6] nss-myhostname: " Saul Wold
2014-12-23 22:57 ` [PATCH 0/6] Updates and bug fixes Saul Wold
2014-12-24 0:27 ` Richard Purdie [this message]
2014-12-24 0:48 ` Saul Wold
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=1419380836.6428.7.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=sgw@linux.intel.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