From: "Vester Thacker" <vester.thacker@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: [9fans] Thoughts about Plan 9 development, UAT, and production.
Date: Fri, 11 May 2007 19:25:21 +0900 [thread overview]
Message-ID: <32a656c20705110325u72eea02emb2b0a35f47282375@mail.gmail.com> (raw)
Would it be beneficial to have public accessible revision control
servers for Plan 9 development and UAT?
I`m interested in the developers` thoughts about access, revision
control, and moving forward as a community. Are people having a
problem with the present model? If so, then what are your suggestions
for improvements?
Uriel, this isn`t intended as an opportunity for you or anyone else to
rant. I want to know what everyone else thinks for a change. :)
If all is well, I`d like to know that too.
Regards,
Vester
next reply other threads:[~2007-05-11 10:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-11 10:25 Vester Thacker [this message]
2007-05-11 17:42 ` lucio
2007-05-11 18:17 ` Christopher Nielsen
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=32a656c20705110325u72eea02emb2b0a35f47282375@mail.gmail.com \
--to=vester.thacker@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).