qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: Fabiano Rosas <farosas@suse.de>
Cc: qemu-devel@nongnu.org,
	"Daniel P . Berrangé" <berrange@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Thomas Huth" <thuth@redhat.com>
Subject: Re: [PATCH v4 0/3] migration & CI: Add a CI job for migration compat testing
Date: Mon, 22 Jan 2024 18:23:41 +0800	[thread overview]
Message-ID: <Za5CLca2c6kYDpR2@x1n> (raw)
In-Reply-To: <87v87pzdck.fsf@suse.de>

On Fri, Jan 19, 2024 at 10:01:31AM -0300, Fabiano Rosas wrote:
> I mentioned this at the bottom of the commit message for patch 2/3. You
> need to push your tags. Otherwise your fork on gitlab won't have
> knowledge of v8.2.0.

Oops, my fault.  Yeah it works now; I queued this into staging.

Thanks,

-- 
Peter Xu



      reply	other threads:[~2024-01-22 10:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-18 16:49 [PATCH v4 0/3] migration & CI: Add a CI job for migration compat testing Fabiano Rosas
2024-01-18 16:49 ` [PATCH v4 1/3] tests/qtest/migration: Don't use -cpu max for aarch64 Fabiano Rosas
2024-01-18 16:49 ` [PATCH v4 2/3] ci: Add a migration compatibility test job Fabiano Rosas
2024-01-18 16:49 ` [PATCH v4 3/3] ci: Disable migration compatibility tests for aarch64 Fabiano Rosas
2024-01-19  4:01   ` Peter Xu
2024-01-19 13:04     ` Fabiano Rosas
2024-01-20  2:35       ` Peter Xu
2024-01-19  9:11 ` [PATCH v4 0/3] migration & CI: Add a CI job for migration compat testing Peter Xu
2024-01-19 13:01   ` Fabiano Rosas
2024-01-22 10:23     ` Peter Xu [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=Za5CLca2c6kYDpR2@x1n \
    --to=peterx@redhat.com \
    --cc=berrange@redhat.com \
    --cc=farosas@suse.de \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.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;
as well as URLs for NNTP newsgroup(s).