From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [RFC PATCH] ci: ensure that all jobs use a shallow clone
Date: Fri, 8 Jan 2021 11:10:24 +0000 [thread overview]
Message-ID: <20210108111024.GG1082385@redhat.com> (raw)
In-Reply-To: <29312927-eb21-dab0-cea2-c2c9139a3e0c@redhat.com>
On Fri, Jan 08, 2021 at 12:06:01PM +0100, Thomas Huth wrote:
> On 08/01/2021 11.16, Daniel P. Berrangé wrote:
>
> > IOW, despite travis giving us non-x86 builders, it is doomed to be
> > unusuable, unless we can convince them to give us a *massively*
> > larger free credit allowance on the qemu account.
> I think convincing them to do this will be very hard. I've tried to apply to
> the free OSS credits for my account, and in the mail that I've got back
> after a couple of weeks, they wrote that "Project must not be sponsored by a
> commercial company or organization (monetary or with employees paid to work
> on the project)" to qualify for the free credits. That doesn't sound like
> they'll accept QEMU, I think.
Yeah that makes their OSS program unviable for any project which isn't
essentially just a single person free time effort.
Lets drop Travis and not waste any more time on this.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2021-01-08 11:11 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
2021-01-08 10:16 ` Daniel P. Berrangé
2021-01-08 11:06 ` Thomas Huth
2021-01-08 11:10 ` Daniel P. Berrangé [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=20210108111024.GG1082385@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=pbonzini@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).