9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Marc Cinq Brillant" <marc.brillant@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] New to plan 9: what next?
Date: Tue, 19 Feb 2008 22:23:22 -0800	[thread overview]
Message-ID: <756044280802192223w41fc7516j3bdfcfca60947a38@mail.gmail.com> (raw)
In-Reply-To: <EC01D9B3-2BCC-4FCC-AC57-6F291F629947@mac.com>

You more annoying than 99% of people.

I save Uriel time - you fuck off!

2008/2/19, Pietro Gagliardi <pietro10@mac.com>:
> Or perhaps someone should write a book aimed at newbies on using Plan
> 9 from Bell Labs. It would be called "Using Plan 9 from Bell Labs,"
> typeset in troff, and not go into technical details.
>
> On Feb 19, 2008, at 11:56 PM, Lorenzo Fernando Bivens de la Fuente
> wrote:
>
> > Perhaps there could be an "autoanswer" mail account...
> > newbie@plan9.net or something... :P
> >
> > On Feb 20, 2008 4:44 AM,  <lucio@proxima.alt.za> wrote:
> >>
> >>> On Feb 19, 2008 9:50 PM,  <john@csplan9.rit.edu> wrote:
> >>>> Maybe somebody should set up a script that looks for emails with
> >>>> subjects similar to "new to Plan 9", "Plan 9 newbie", etc. and
> >>>> sends a message with links to the wiki.
> >>>> I'm only half joking.
> >>>>
> >>>> John
> >>>>
> >>>>
> >>>
> >>> first that.
> >>>
> >>> iru
> >>
> >> We used to have FAQs in the good old days.  The Plan 9 one has been
> >> deceased a while, maybe we should distil the wiki knowledge into it
> >> for a shorter, more static document?  I'm not volunteering, but if
> >> others think it's worthwhile I'll certainly be willing to assist.
> >>
> >> ++L
> >>
> >>
>
>


--
Ce n'est pas une chanson d'amour


  parent reply	other threads:[~2008-02-20  6:23 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-19 22:58 devrin talen
2008-02-19 23:11 ` Pietro Gagliardi
2008-02-20  0:00   ` Martin Neubauer
2008-02-20  0:37     ` Federico G. Benavento
2008-02-20  0:50       ` john
2008-02-20  1:06         ` Iruata Souza
2008-02-20  4:44           ` lucio
2008-02-20  4:56             ` Lorenzo Fernando Bivens de la Fuente
2008-02-20  5:10               ` Pietro Gagliardi
2008-02-20  5:14                 ` andrey mirtchovski
2008-02-20  5:47                   ` Lorenzo Fernando Bivens de la Fuente
2008-02-20  6:23                 ` Marc Cinq Brillant [this message]
2008-02-20  7:32                 ` Gorka Guardiola
2008-02-20  8:20                   ` Bruce Ellis
2008-02-20 18:13                 ` Russ Cox
2008-02-20 22:08                   ` Pietro Gagliardi
2008-02-21  0:08                     ` hiro
2008-02-21  0:01                   ` Benjamin Huntsman
2008-02-21  3:09                     ` Bruce Ellis
2008-02-21  4:44                     ` lucio
2008-02-20  0:40   ` Iruata Souza
2008-02-20  0:48     ` devrin talen
2008-02-20  4:28       ` Iruata Souza
2008-02-20  9:39       ` Kernel Panic
2008-02-20 13:29         ` Pietro Gagliardi
2008-02-20 15:38           ` Iruata Souza
2008-02-19 23:34 ` john
2008-02-20  0:41 ` Iruata Souza

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=756044280802192223w41fc7516j3bdfcfca60947a38@mail.gmail.com \
    --to=marc.brillant@gmail.com \
    --cc=9fans@cse.psu.edu \
    /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).