From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Neal Gompa <ngompa13@gmail.com>
Cc: unit193@ubuntu.com, Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
Andy Whitcroft <apw@canonical.com>,
Ubuntu Kernel Team <kernel-team@lists.ubuntu.com>,
Martin Hauke <mardnh@gmx.de>, Joe Doss <joe@solidadmin.com>,
WireGuard mailing list <wireguard@lists.zx2c4.com>,
Carl George <carl@redhat.com>
Subject: Re: Adding Debian, Ubuntu, OpenSUSE, RHEL, CentOS kernels to WireGuard CI: Seeking URLs
Date: Sat, 23 May 2020 18:01:39 -0600 [thread overview]
Message-ID: <CAHmME9rOs221DN_KC4N0MJ+L9grX9Yx1fjypKM9qT-ixgo9oHA@mail.gmail.com> (raw)
In-Reply-To: <CAEg-Je8=PEek1d9ZvK9Fqnbm4TOzZU4hKvFL0zVd6k2w0ionvQ@mail.gmail.com>
On Sat, May 23, 2020 at 5:50 AM Neal Gompa <ngompa13@gmail.com> wrote:
>
> On Sat, May 23, 2020 at 3:21 AM Jason A. Donenfeld <Jason@zx2c4.com> wrote:
> >
> > Hi Neal,
> >
> > Thanks for these very helpful instructions. In trying to implement
> > this, one snag I encountered was that the .src.rpm file has inside of
> > it the linux-{version}.tar.xz file that I actually want. Is there
> > anywhere on the internet that hosts these .tar.xz files directly?
> >
>
> There *is*, but that starts getting into using the CentOS Git system
> more directly. Per your original email, you weren't interested in that
> path, so I didn't go there.
Well, one trick is that most web git viewers (such as cgit) can
produce a tarball on the fly from a URL. Something like this exist
here?
next prev parent reply other threads:[~2020-05-24 2:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-22 8:04 Jason A. Donenfeld
2020-05-22 8:44 ` Jason A. Donenfeld
2020-05-23 5:59 ` Jason A. Donenfeld
2020-05-22 12:43 ` Georg Faerber
2020-05-23 12:31 ` Georg Faerber
2020-05-23 7:07 ` Neal Gompa
2020-05-23 7:21 ` Jason A. Donenfeld
2020-05-23 11:49 ` Neal Gompa
2020-05-24 0:01 ` Jason A. Donenfeld [this message]
2020-05-24 0:20 ` Neal Gompa
2020-05-24 1:10 ` Jason A. Donenfeld
2020-05-24 1:41 ` Jason A. Donenfeld
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=CAHmME9rOs221DN_KC4N0MJ+L9grX9Yx1fjypKM9qT-ixgo9oHA@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=apw@canonical.com \
--cc=carl@redhat.com \
--cc=dkg@fifthhorseman.net \
--cc=joe@solidadmin.com \
--cc=kernel-team@lists.ubuntu.com \
--cc=mardnh@gmx.de \
--cc=ngompa13@gmail.com \
--cc=unit193@ubuntu.com \
--cc=wireguard@lists.zx2c4.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).