9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Francisco J Ballesteros <nemo.mbox@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Closed nix development is an insult
Date: Fri,  6 Sep 2013 11:52:35 +0200	[thread overview]
Message-ID: <2800EDE5-85A9-4C2F-A49F-8BF510FBF08C@gmail.com> (raw)
In-Reply-To: <4db80b148563a9d49f4fcfaca3997057@hamnavoe.com>

[-- Attachment #1: Type: text/plain, Size: 584 bytes --]


On Sep 6, 2013, at 10:49 AM, Richard Miller <9fans@hamnavoe.com> wrote:

>> tl;dr: as far as i know, there is no private nix development going on,
> 
> Aha, the fact that you don't know proves that it's private. ☺

As are most the files I open in my editor, until at some point I do a Put and
others can access them. But in that interval, development is secretly confined
to my terminal. Yes. That does not mean I'll keep the file for me forever.

Also, yes, I'm usually the one who can better judge when doing a Put in my
editor is a good idea. Sorry about that.



[-- Attachment #2: Type: text/html, Size: 2172 bytes --]

  reply	other threads:[~2013-09-06  9:52 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-05 22:13 Aram Hăvărneanu
2013-09-05 22:35 ` erik quanstrom
2013-09-06  8:49   ` Richard Miller
2013-09-06  9:52     ` Francisco J Ballesteros [this message]
2013-09-06 10:24       ` hiro
2013-09-05 22:36 ` Francisco J Ballesteros
2013-09-05 23:07   ` Kurt H Maier
2013-09-06  8:27     ` Steve Simon
2013-09-06 22:59       ` BurnZeZ
2013-09-06 23:00       ` Francisco J Ballesteros
2013-09-07 19:15         ` Christopher Nielsen
2013-09-06 23:10       ` Kurt H Maier
2013-09-06 23:35       ` Aram Hăvărneanu
2013-09-06 23:42         ` Nemo
2013-09-07  2:49         ` erik quanstrom
2013-09-07  4:06           ` Devon H. O'Dell
2013-09-07  4:36             ` Bruce Ellis
2013-09-07  6:24               ` pmarin
2013-09-07 13:21               ` Kurt H Maier
2013-09-07 13:28                 ` Bruce Ellis
2013-09-07 13:33                   ` Kurt H Maier
2013-09-07 13:41                     ` Bruce Ellis
2013-09-07 13:56                       ` Aram Hăvărneanu
2013-09-07 14:32                         ` Bruce Ellis
2013-09-07 14:52                         ` Latchesar Ionkov
2013-09-07 16:28                         ` erik quanstrom
2013-09-07 17:01                           ` Latchesar Ionkov
2013-09-07 17:48                         ` Gorka Guardiola
2013-09-07 20:46                         ` Charles Forsyth
2013-09-07 23:47                           ` Matthew Veety
2013-09-08  0:19                             ` Charles Forsyth
2013-09-08  7:00                               ` Bruce Ellis
2013-09-07 14:58           ` Anthony Sorace
2013-09-07 15:05             ` Bruce Ellis
2013-09-07 15:14             ` tlaronde
2013-09-07 15:46               ` lucio
2013-09-07 16:06                 ` tlaronde
2013-09-07 16:40                   ` lucio
2013-09-07 16:56                     ` Ethan Grammatikidis
2013-09-07 17:45                       ` lucio
2013-09-07 17:50                         ` lucio
2013-09-07 16:57                     ` tlaronde
2013-09-07 16:35         ` Ethan Grammatikidis
2013-09-06 23:48 Terry Wendt

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=2800EDE5-85A9-4C2F-A49F-8BF510FBF08C@gmail.com \
    --to=nemo.mbox@gmail.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).