From: Wes Kussmaul <wes@ReliableID.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Plan 9 5th Edition
Date: Sun, 20 Nov 2016 21:19:13 -0500 [thread overview]
Message-ID: <dfa91903-a96c-72d7-98c7-f261cbf9a8de@ReliableID.com> (raw)
In-Reply-To: <B75D9C72-E5B5-4F6D-A58C-9B2DFA3DB4C3@pobox.com>
On 11/19/2016 05:27 PM, David Arnold wrote:
> On 17 Nov 2016, at 12:18, Kurt H Maier wrote:
>> On Wed, Nov 16, 2016 at 07:55:38PM -0500, Charlie Lin wrote:
>
>>> Also does anyone want to host the source tree in a repository?
>>
>> This sounds like a lot of work. Who would undertake this??
>
> GitHub, GitLab, or BitBucket all provide gratis repository hosting for Git and/or Mercurial. If one of those were adopted, the work involved for ongoing maintenance is minimal.
We use gitlab on our team for both repos and task management. I'd be
happy to create and maintain a group for Plan9.
In fact while I was thinking about it I just did. It's at
https://gitlab.com/nine-continent
--
Wes Kussmaul
The Authenticity Institute
738 Main Street
Waltham, MA 02451
office +1 781 790 1674
mobile +1 781 330 1881
THIS COMMUNICATION IS INTENDED ONLY FOR THE USE OF THE PERSON TO WHOM IT
IS ADDRESSED.
If it was addressed incorrectly there's not much I can do but ask you
politely to pretend you didn't see it. Any disclaimer suggesting that
the sender has some kind of recourse is just wishful thinking.
If I had a message from you that was digitally signed using your Osmio
VRD™ identity credential from the Osmio Vital Records Department
(http://osmio.ch), we could easily and at no cost exchange
encrypted messages and files with each other.
next prev parent reply other threads:[~2016-11-21 2:19 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 22:27 Charlie Lin
2016-11-16 22:43 ` Stanley Lieber
2016-11-16 22:44 ` Ole-Hjalmar Kristensen
2016-11-16 23:53 ` Chris McGee
2016-11-17 0:34 ` James A. Robinson
2016-11-17 1:14 ` Charlie Lin
2016-11-17 16:16 ` Dave MacFarlane
2016-11-17 17:50 ` Ori Bernstein
2016-11-17 20:29 ` Chris McGee
2016-11-17 20:32 ` Ori Bernstein
2016-11-17 20:31 ` Chris McGee
2016-11-17 0:21 ` Charlie Lin
2016-11-17 0:30 ` Kurt H Maier
2016-11-18 19:54 ` Charlie Lin
2016-11-18 19:57 ` Charlie Lin
2016-11-18 19:58 ` Charlie Lin
2016-11-18 22:26 ` hiro
2016-11-18 22:28 ` hiro
2016-11-19 16:57 ` cinap_lenrek
2016-11-19 18:42 ` Steve Simon
[not found] ` <CAEVxPTMKBpWFEGr-k1diNa2BVgCjsL1g-OPZdhn9LmEn3uLB5g@mail.gmail.com>
[not found] ` <CAEVxPTN_KZn_4+s1xr-uiDzEY72wf2AtrXYN_FDgdaPbyqpLbw@mail.gmail.com>
2016-11-18 20:07 ` Jules Merit
2016-11-17 0:55 ` Charlie Lin
2016-11-17 1:02 ` Stanley Lieber
2016-11-17 1:18 ` Kurt H Maier
2016-11-19 22:27 ` David Arnold
2016-11-20 2:39 ` hiro
2016-11-20 4:26 ` Ryan Gonzalez
2016-11-20 6:22 ` Kurt H Maier
2016-11-20 6:54 ` James A. Robinson
2016-11-20 9:44 ` hiro
2016-11-21 2:19 ` Wes Kussmaul [this message]
2016-11-21 8:02 ` hiro
2016-11-21 8:02 ` Kurt H Maier
2016-11-21 8:46 ` Sigrid Haflinadóttir
2016-11-21 15:08 ` Wes Kussmaul
2016-11-21 15:42 ` Chris McGee
2016-11-19 20:19 ` Charlie Lin
2016-11-19 20:37 ` Charlie Lin
2016-11-19 21:51 ` Steve Simon
2016-11-19 22:27 ` Stanley Lieber
2016-11-20 15:23 ` Chris McGee
2016-11-20 18:09 ` hiro
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=dfa91903-a96c-72d7-98c7-f261cbf9a8de@ReliableID.com \
--to=wes@reliableid.com \
--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).