From: Anthony Sorace <a@9srv.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Starting a blog on plan 9
Date: Tue, 8 May 2012 11:55:51 -0400 [thread overview]
Message-ID: <98C72F53-1E58-492B-A0E1-C56779CAAAA6@9srv.net> (raw)
In-Reply-To: <7e93404c-01f6-419a-9f1a-9aee147d4772@iu9g2000pbc.googlegroups.com>
[-- Attachment #1: Type: text/plain, Size: 667 bytes --]
This looks pretty well done - a good beginner's hands-on view to
getting to know the system.
In the interest of addressing the "resources ... all in one place" issue,
though, I would encourage you to also contribute to the wiki[1]. I'm
not suggesting everything you're putting on your blog belongs on the
wiki (the wiki isn't really good for the sort of narrative sense good
blogs give), but it is the best place for centralized resources. There
is a wiki page with instructions on how to edit it[2].
Anthony
[1] http://www.plan9.bell-labs.com/wiki/plan9/plan_9_wiki/
[2] http://www.plan9.bell-labs.com/wiki/plan9/acme_wiki_instructions/index.html
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 210 bytes --]
next prev parent reply other threads:[~2012-05-08 15:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 9:34 IainWS
2012-05-08 10:19 ` Nicolas Bercher
2012-05-08 14:44 ` Tassilo Philipp
2012-05-08 14:51 ` Christoph Lohmann
2012-05-08 15:55 ` Anthony Sorace [this message]
2012-05-08 16:15 ` John Floren
2012-05-08 20:23 ` Yaroslav
2012-05-09 8:49 ` IainWS
2012-05-09 8:49 ` IainWS
2012-05-09 18:49 ` steve
[not found] ` <4753aa01-47ee-4945-aa82-9da4691190c3@sm6g2000pbc.googlegroups.co>
2012-05-09 12:09 ` erik quanstrom
2012-05-09 12:16 ` Russ Cox
2012-05-09 13:27 ` Charles Forsyth
2012-05-09 15:04 ` dexen deVries
2012-05-10 11:35 ` IainWS
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=98C72F53-1E58-492B-A0E1-C56779CAAAA6@9srv.net \
--to=a@9srv.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).