From: Saul Wold <sgw@linux.intel.com>
To: Phil Blundell <pb@pbcl.net>,
oe-core <openembedded-core@lists.openembedded.org>
Subject: Re: [oe-commits] Upgrade Helper : base-passwd: upgrade to 3.5.29
Date: Mon, 13 Jan 2014 10:32:14 -0800 [thread overview]
Message-ID: <52D4312E.6030005@linux.intel.com> (raw)
In-Reply-To: <1389617286.9182.181.camel@phil-desktop.brightsign>
On 01/13/2014 04:48 AM, Phil Blundell wrote:
> The new version introduced by this patch doesn't seem to actually exist
> at the SRC_URI. (ftp.debian.org currently has 3.5.28, 3.5.30 and 3.5.31
> but not 3.5.29.)
>
Seems they did a quick succession of updates and removed the .29
version. I am working on the .31 update
> Also, as far as I can tell, this patch wasn't ever posted to the list
> for review and the alleged author's email address of "uh@not.set"
> doesn't sound entirely plausible.
>
My mistake, I did the update built it locally and it was included as
part of a MUT / C-Pull.
Sau!
>
>
>> Module: openembedded-core.git
>> Branch: master
>> Commit: 7c79e70d3a803f2ccb9b9c6ed2134019631672fd
>> URL: http://git.openembedded.org/?p=openembedded-core.git&a=commit;h=7c79e70d3a803f2ccb9b9c6ed2134019631672fd
>>
>> Author: Upgrade Helper <uh at not.set>
>> Date: Sat Jan 4 11:44:14 2014 +0200
>>
>> base-passwd: upgrade to 3.5.29
>>
>> Signed-off-by: Saul Wold <sgw at linux.intel.com>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
>
prev parent reply other threads:[~2014-01-13 18:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 12:48 [oe-commits] Upgrade Helper : base-passwd: upgrade to 3.5.29 Phil Blundell
2014-01-13 18:32 ` Saul Wold [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=52D4312E.6030005@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=pb@pbcl.net \
/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