From: Daniel Henrique Barboza <danielhb413@gmail.com>
To: Richard Henderson <richard.henderson@linaro.org>, qemu-devel@nongnu.org
Cc: qemu-ppc@nongnu.org, peter.maydell@linaro.org
Subject: Re: [PULL 0/3] ppc queue
Date: Thu, 28 Jul 2022 17:32:01 -0300 [thread overview]
Message-ID: <03379d76-a85b-3d1b-c334-ddb02823c418@gmail.com> (raw)
In-Reply-To: <8a7f394c-55ac-09cb-91b0-41f5d4c12fff@linaro.org>
On 7/28/22 17:18, Richard Henderson wrote:
> On 7/28/22 09:55, Daniel Henrique Barboza wrote:
>> https://gitlab.com/danielhb/qemu.git pull-ppc-20220728
>
> fatal: couldn't find remote ref pull-ppc-20220728
>
>
> Did you forget to push the tag to gitlab?
I guess I mistyped the credentials when running make-pullreq.sh and the
tag wasn't pushed. Can you try again? It is pushed now:
https://gitlab.com/danielhb/qemu/-/commits/pull-ppc-20220728
Thanks,
Daniel
>
>
> r~
next prev parent reply other threads:[~2022-07-28 20:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-28 16:55 [PULL 0/3] ppc queue Daniel Henrique Barboza
2022-07-28 16:55 ` [PULL 1/3] hw/ppc: check if spapr_drc_index() returns NULL in spapr_nvdimm.c Daniel Henrique Barboza
2022-07-28 16:55 ` [PULL 2/3] hw/ppc/ppc440_uc: Initialize length passed to cpu_physical_memory_map() Daniel Henrique Barboza
2022-07-28 16:55 ` [PULL 3/3] target/ppc: Implement new wait variants Daniel Henrique Barboza
2022-07-28 20:18 ` [PULL 0/3] ppc queue Richard Henderson
2022-07-28 20:32 ` Daniel Henrique Barboza [this message]
2022-07-29 0:28 ` Richard Henderson
-- strict thread matches above, loose matches on Subject: below --
2023-09-18 13:29 Daniel Henrique Barboza
2023-09-19 19:13 ` Stefan Hajnoczi
2022-04-04 14:38 Cédric Le Goater
2022-04-04 19:44 ` Peter Maydell
2022-03-21 6:44 Cédric Le Goater
2022-03-21 15:26 ` Peter Maydell
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=03379d76-a85b-3d1b-c334-ddb02823c418@gmail.com \
--to=danielhb413@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=richard.henderson@linaro.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).