From: Steve Simon <steve@quintile.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] sources down
Date: Fri, 28 Dec 2018 21:51:03 +0000 [thread overview]
Message-ID: <F39D3B21-8504-403D-8666-FD8A7EE6FBBC@quintile.net> (raw)
In-Reply-To: <CAJSxfmKUedDcCzGee9F8oMvPtJtfeUizHEUAwueRbKE2kh-5og@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1190 bytes --]
i have a copy if the diffs russ’s web pages used, though i dont think the annotations are included. it lived on russ’s server i think, not the labs one.
maybe its on the internet archive?
-Steve
> On 28 Dec 2018, at 9:23 pm, Skip Tavakkolian <skip.tavakkolian@gmail.com> wrote:
>
> In all seriousness, it's not too difficult to integrate in. I used Russ' letsencrypt package before this one. Both have been straight forward. There are samples too.
>
> With Go modules and vendoring, package version can be locked in (notwithstanding security fixes)
>
>> On Fri, Dec 28, 2018, 1:15 PM Skip Tavakkolian <skip.tavakkolian@gmail.com wrote:
>> It's all relative. For example, compared to the current President of the United States, this API is extremely stable :)
>>
>>> On Fri, Dec 28, 2018, 11:58 AM Ethan Gardener <eekee57@fastmail.fm wrote:
>>> On Fri, Dec 28, 2018, at 7:43 PM, Skip Tavakkolian wrote:
>>> > while I'm thinking about it, is it possible for 9legacy.org to use letsencrypt? Go's acme/autocert package (golang.org/x/crypto/acme/autocert) works great.
>>>
>>> "This package is a work in progress and makes no API stability promises."
>>>
[-- Attachment #2: Type: text/html, Size: 2366 bytes --]
next prev parent reply other threads:[~2018-12-28 21:51 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-28 19:07 hiro
2018-12-28 19:29 ` Steve Simon
2018-12-28 19:43 ` Skip Tavakkolian
2018-12-28 19:57 ` Ethan Gardener
2018-12-28 20:58 ` hiro
2018-12-28 23:00 ` David du Colombier
2018-12-28 21:15 ` Skip Tavakkolian
2018-12-28 21:23 ` Skip Tavakkolian
2018-12-28 21:51 ` Steve Simon [this message]
2018-12-29 10:05 ` hiro
2018-12-29 10:09 ` Steve Simon
2018-12-29 13:18 ` David du Colombier
2018-12-29 20:29 ` hiro
2018-12-30 9:46 ` David du Colombier
2018-12-30 22:45 ` Steve Simon
2018-12-30 22:52 ` David du Colombier
2018-12-31 8:21 ` Devon H. O'Dell
2018-12-31 8:51 ` Lucio De Re
2018-12-31 9:50 ` Steve Simon
2018-12-31 10:48 ` David du Colombier
2018-12-31 12:34 ` hiro
2018-12-31 12:46 ` Lucio De Re
2018-12-31 14:02 ` hiro
2018-12-31 6:58 ` arnold
2018-12-31 8:00 ` Kurt H Maier
2018-12-31 9:49 ` arnold
2018-12-31 11:11 ` David du Colombier
2018-12-31 12:26 ` arnold
2018-12-29 9:57 ` hiro
2018-12-29 8:59 ` Ethan Gardener
2018-12-29 9:53 ` hiro
2018-12-28 23:05 ` David du Colombier
2018-12-29 3:58 ` Lucio De Re
2018-12-29 9:14 ` Ethan Gardener
2018-12-29 9:30 ` Lucio De Re
-- strict thread matches above, loose matches on Subject: below --
2018-12-31 15:48 sl
2008-11-30 12:33 [9fans] Sources down Rodolfo kix Garcia
2008-11-30 12:38 ` Richard Miller
2008-11-30 19:09 ` Roman Zhukov
2008-11-30 19:56 ` Charles Forsyth
2008-11-30 20:34 ` geoff
2008-11-30 20:37 ` Francisco J Ballesteros
2006-11-04 2:43 [9fans] sources down geoff
2006-11-04 8:05 ` geoff
2006-11-06 3:42 ` geoff
2006-11-06 13:19 ` erik quanstrom
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=F39D3B21-8504-403D-8666-FD8A7EE6FBBC@quintile.net \
--to=steve@quintile.net \
--cc=9fans@9fans.net \
/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).