From: Bruno Wolff III <bruno@wolff.to>
To: Aleksa Sarai <cyphar@cyphar.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: The Linux Plumbers Conference videos are up
Date: Tue, 4 Dec 2018 02:15:20 -0600 [thread overview]
Message-ID: <20181204081520.GB9036@wolff.to> (raw)
In-Reply-To: <20181204080347.GA9036@wolff.to>
On Tue, Dec 04, 2018 at 02:03:47 -0600,
Bruno Wolff III <bruno@wolff.to> wrote:
>
>Thanks. That explains why I can't get there, even though there is a
>path. That drop down appears to only work with javascript enabled,
>which I don't normally have enabled.
This might be a gecko bug. When I use lynx I see the dropdown. The code
doesn't look like it should need javascript to be displayed.
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
prev parent reply other threads:[~2018-12-04 8:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 21:46 Bruno Wolff III
2018-12-04 0:47 ` Jason A. Donenfeld
2018-12-04 7:15 ` Bruno Wolff III
2018-12-04 7:55 ` Aleksa Sarai
2018-12-04 8:03 ` Bruno Wolff III
2018-12-04 8:15 ` Bruno Wolff III [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=20181204081520.GB9036@wolff.to \
--to=bruno@wolff.to \
--cc=cyphar@cyphar.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).