From: Thomas Huth <thuth@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Michael Roth" <michael.roth@amd.com>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Willian Rampazzo" <willianr@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH] travis.yml: Remove the "Release tarball" job
Date: Fri, 17 Sep 2021 13:42:56 +0200 [thread overview]
Message-ID: <9a941135-a659-bf8e-6b4f-bc7e297060c0@redhat.com> (raw)
In-Reply-To: <CAAdtpL7DkZyE7z-M2trjnXj0mpry95Y-T7-WahgxWg-jfg9gCg@mail.gmail.com>
On 17/09/2021 13.25, Philippe Mathieu-Daudé wrote:
> Le ven. 17 sept. 2021 11:48, Thomas Huth <thuth@redhat.com
> <mailto:thuth@redhat.com>> a écrit :
>
> This is a leftover from the days when we were using Travis excessively,
> but since x86 jobs are not really usable there anymore, this job has
> likely never been used since many months. Let's simply remove it now.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com <mailto:thuth@redhat.com>>
> ---
> .travis.yml | 23 -----------------------
> 1 file changed, 23 deletions(-)
>
> Do we have the equivalent job on GitLab?
I'm not aware of any. But since this job was only running on v* tags anyway,
it likely does not make much sense to translate it 1:1 to a gitlab job. But
maybe Michael could suggest something similar if it's helpful for making
sure the release tarballs do no regress?
Thomas
next prev parent reply other threads:[~2021-09-17 11:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-17 9:48 [PATCH] travis.yml: Remove the "Release tarball" job Thomas Huth
2021-09-17 10:00 ` Daniel P. Berrangé
2021-09-17 11:19 ` Alex Bennée
2021-09-17 11:25 ` Philippe Mathieu-Daudé
2021-09-17 11:42 ` Thomas Huth [this message]
2021-09-17 12:37 ` Philippe Mathieu-Daudé
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=9a941135-a659-bf8e-6b4f-bc7e297060c0@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=f4bug@amsat.org \
--cc=michael.roth@amd.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=wainersm@redhat.com \
--cc=willianr@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).