All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>, kvm@vger.kernel.org
Cc: Janosch Frank <frankja@linux.ibm.com>,
	Andrew Jones <drjones@redhat.com>,
	Laurent Vivier <lvivier@redhat.com>,
	David Hildenbrand <david@redhat.com>
Subject: Re: [kvm-unit-tests PULL 00/11] s390x and generic script updates
Date: Tue, 29 Sep 2020 10:47:16 +0200	[thread overview]
Message-ID: <c7b332f9-b81e-1bc8-7337-d525e8d033c5@redhat.com> (raw)
In-Reply-To: <fa187ed1-0e02-62e5-ba27-4f64782b3cfd@redhat.com>

On 29/09/2020 10.38, Paolo Bonzini wrote:
> On 28/09/20 19:49, Thomas Huth wrote:
>>  Hi Paolo,
>>
>> the following changes since commit 58c94d57a51a6927a68e3f09627b2d85e3404c0f:
>>
>>   travis.yml: Use TRAVIS_BUILD_DIR to refer to the top directory (2020-09-25 10:00:36 +0200)
>>
>> are available in the Git repository at:
>>
>>   https://gitlab.com/huth/kvm-unit-tests.git tags/pull-request-2020-09-28
>>
>> for you to fetch changes up to b508e1147055255ecce93a95916363bda8c8f299:
>>
>>   scripts/arch-run: use ncat rather than nc. (2020-09-28 15:03:50 +0200)
[...]
> Pulled, thanks (for now to my clone; waiting for CI to complete).
> Should we switch to Gitlab merge requests for pull requests only (i.e.
> patches still go on the mailing list)?

Fine for me, though I'm not sure whether the other maintainers are
already using gitlab or not... And do we need e-mail notifications for
such merge requests sent to the mailing list, in case anybody else still
wants to object?

 Thomas


  reply	other threads:[~2020-09-29  8:47 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-28 17:49 [kvm-unit-tests PULL 00/11] s390x and generic script updates Thomas Huth
2020-09-28 17:49 ` [kvm-unit-tests PULL 01/11] runtime.bash: remove outdated comment Thomas Huth
2020-09-28 17:49 ` [kvm-unit-tests PULL 02/11] Use same test names in the default and the TAP13 output format Thomas Huth
2020-09-28 17:49 ` [kvm-unit-tests PULL 03/11] configure: Add a check for the bash version Thomas Huth
2020-09-28 17:49 ` [kvm-unit-tests PULL 04/11] travis.yml: Update from Bionic to Focal Thomas Huth
2020-09-28 17:49 ` [kvm-unit-tests PULL 05/11] travis.yml: Update the list of s390x tests Thomas Huth
2020-09-28 17:49 ` [kvm-unit-tests PULL 06/11] common.bash: run `cmd` only if a test case was found Thomas Huth
2020-09-28 17:49 ` [kvm-unit-tests PULL 07/11] scripts: add support for architecture dependent functions Thomas Huth
2020-09-28 17:49 ` [kvm-unit-tests PULL 08/11] run_tests/mkstandalone: add arch_cmd hook Thomas Huth
2020-09-28 17:49 ` [kvm-unit-tests PULL 09/11] s390x: add Protected VM support Thomas Huth
2020-09-28 17:49 ` [kvm-unit-tests PULL 10/11] s390x/selftest: Fix constraint of inline assembly Thomas Huth
2020-09-28 17:49 ` [kvm-unit-tests PULL 11/11] scripts/arch-run: use ncat rather than nc Thomas Huth
2020-09-29  8:38 ` [kvm-unit-tests PULL 00/11] s390x and generic script updates Paolo Bonzini
2020-09-29  8:47   ` Thomas Huth [this message]
2020-09-29  8:49   ` Janosch Frank
2020-09-29  8:58     ` Thomas Huth
2020-09-29  9:06       ` Paolo Bonzini
2020-10-01  9:21 ` Paolo Bonzini

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=c7b332f9-b81e-1bc8-7337-d525e8d033c5@redhat.com \
    --to=thuth@redhat.com \
    --cc=david@redhat.com \
    --cc=drjones@redhat.com \
    --cc=frankja@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=lvivier@redhat.com \
    --cc=pbonzini@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 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.