qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
	"Daniel P. Berrangé" <berrange@redhat.com>,
	qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [RFC PATCH] ci: ensure that all jobs use a shallow clone
Date: Thu, 7 Jan 2021 20:23:49 +0100	[thread overview]
Message-ID: <CABgObfZt-8gG3c4WTZqd0Ls0VEe43MFc_mFuykoZvDP2ZGu0gA@mail.gmail.com> (raw)
In-Reply-To: <dff4499e-eb4d-f96b-5f82-51352561d231@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 526 bytes --]

Il gio 7 gen 2021, 20:05 Thomas Huth <thuth@redhat.com> ha scritto:

> on travis-ci.com you can
> only get free CI minutes for non-sponsored FOSS projects.
> So let's simply not worry about Travis-CI anymore.
>
> Maybe we could rather disable shippable now that we support the cross
> container builds on gitlab-ci, too?
>

With pleasure, starting this discussion was an intended possible side
effect of the patch. :)

The main issue with Travis is the non-x86 builders, which have no
alternative yet.

Paolo


>   Thomas
>
>

[-- Attachment #2: Type: text/html, Size: 1283 bytes --]

  reply	other threads:[~2021-01-07 19:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-07 17:17 [RFC PATCH] ci: ensure that all jobs use a shallow clone Paolo Bonzini
2021-01-07 18:28 ` Daniel P. Berrangé
2021-01-07 19:05   ` Thomas Huth
2021-01-07 19:23     ` Paolo Bonzini [this message]
2021-01-08 10:16       ` Daniel P. Berrangé
2021-01-08 11:06         ` Thomas Huth
2021-01-08 11:10           ` Daniel P. Berrangé

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=CABgObfZt-8gG3c4WTZqd0Ls0VEe43MFc_mFuykoZvDP2ZGu0gA@mail.gmail.com \
    --to=pbonzini@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=berrange@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --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).