From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 1/1] travis: Temporary workaround for pull rate limit
Date: Mon, 18 Jan 2021 12:38:09 +0100 [thread overview]
Message-ID: <YAVzIdnJ01YfmcSd@yuki.lan> (raw)
In-Reply-To: <YAVkff08KAIh8l+s@pevik>
Hi!
> > I think using gcr.io mirror as a temporary solution is OK. But why we
> > not migrate into Github Actions directly? Now, it is time to this
> > release and do we should apply it before release?
> Lack of time on my side (working on other fixes before release).
Let's push this now, since it's important to have travis working when we
are finalizing the release.
Acked-by: Cyril Hrubis <chrubis@suse.cz>
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2021-01-18 11:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 8:13 [LTP] [PATCH 1/1] travis: Temporary workaround for pull rate limit Petr Vorel
2021-01-18 9:55 ` Yang Xu
2021-01-18 10:35 ` Petr Vorel
2021-01-18 11:38 ` Cyril Hrubis [this message]
2021-01-18 13:46 ` Petr Vorel
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=YAVzIdnJ01YfmcSd@yuki.lan \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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.