From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: openembedded-core@lists.openembedded.org, saul.wold@intel.com
Subject: Re: [PATCH 0/1] linux-yocto/3.2: fix meta SRCREV typo
Date: Mon, 11 Jun 2012 13:52:35 +0100 [thread overview]
Message-ID: <1339419155.30460.21.camel@ted> (raw)
In-Reply-To: <cover.1339164527.git.bruce.ashfield@windriver.com>
On Fri, 2012-06-08 at 10:10 -0400, Bruce Ashfield wrote:
> Richard/Saul,
>
> Argh. I need a brown paper bag .... being focused on 3.4 hid
> thsi from me.
>
> Never underestimate the power of a rebase for inserting fat finger
> errors that are hidden by local layers.
>
> An extraneous character made it into the 3.2 meta SRCREV, which makes
> the fetcher error, even when the kernel isn't being built.
I came to Tom's patch first but a fix has been merged.
Cheers,
Richard
next prev parent reply other threads:[~2012-06-11 13:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-08 14:10 [PATCH 0/1] linux-yocto/3.2: fix meta SRCREV typo Bruce Ashfield
2012-06-08 14:10 ` [PATCH 1/1] " Bruce Ashfield
2012-06-11 12:52 ` Richard Purdie [this message]
2012-06-11 13:00 ` [PATCH 0/1] " Bruce Ashfield
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=1339419155.30460.21.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=bruce.ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=saul.wold@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.