From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [GIT PULL] pseries: Update SLOF firmware image to 20160223
Date: Wed, 24 Feb 2016 19:37:46 +1100 [thread overview]
Message-ID: <56CD6BDA.2030906@ozlabs.ru> (raw)
In-Reply-To: <20160224054531.GK2808@voom.fritz.box>
On 02/24/2016 04:45 PM, David Gibson wrote:
> On Tue, Feb 23, 2016 at 07:25:13PM +1100, Alexey Kardashevskiy wrote:
>>
>> This is expected to go via the powerpc tree at git://github.com/dgibson/qemu.git
>>
>>
>> The following changes since commit 8eb779e4223a18db9838a49ece1bc72cfdfb7761:
>>
>> Merge remote-tracking branch 'remotes/kevin/tags/for-upstream' into staging (2016-02-22 16:55:41 +0000)
>>
>> are available in the git repository at:
>>
>> git@github.com:aik/qemu.git
>>
>> for you to fetch changes up to d618bd06b255fcde2111f5733f48d38f5b2532d6:
>>
>> pseries: Update SLOF firmware image to 20160223 (2016-02-23 18:11:17 +1100)
>
> Erm.. I pulled that remote, but:
>
> $ git show d618bd06b255fcde2111f5733f48d38f5b2532d6
> fatal: bad object d618bd06b255fcde2111f5733f48d38f5b2532d6
>
> Nor can I see these changes in any of the branches.
>
It has qemu-slof-20160223 tag (not a branch) and I can see it via web:
https://github.com/aik/qemu/commit/d618bd06b255fcde2111f5733f48d38f5b2532d6
I am confused now.
--
Alexey
next prev parent reply other threads:[~2016-02-24 8:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 8:25 [Qemu-devel] [GIT PULL] pseries: Update SLOF firmware image to 20160223 Alexey Kardashevskiy
2016-02-24 5:45 ` David Gibson
2016-02-24 8:37 ` Alexey Kardashevskiy [this message]
2016-02-24 9:20 ` David Gibson
2016-02-25 2:38 ` David Gibson
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=56CD6BDA.2030906@ozlabs.ru \
--to=aik@ozlabs.ru \
--cc=david@gibson.dropbear.id.au \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.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;
as well as URLs for NNTP newsgroup(s).