From: "ron minnich" <rminnich@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: [9fans] why I'm messing with python: mercurial
Date: Sat, 23 Dec 2006 22:26:07 -0700 [thread overview]
Message-ID: <13426df10612232126p669bd6eaq1411e0546c5dcd7@mail.gmail.com> (raw)
I feel that Plan 9 could stand to have a reasonable version control
system, which CVS certainly is not. Mecurial is written in python, is
working well for xen, so I thought I'd see if it would work at all in
python on plan9.
First step: errno :-)
thanks
ron
p.s. Give Aki and me a present for the new year: please test our
little minimal linux + xen + plan 9 if you can. I'm using it, and I
think it's quite nice. I can't wait to try out plan 9 + xen on a
dual-core, it's already reasonably fast. Those long kernel build times
under qemu are a thing of the past. Don't forget, free with every copy
you buy, you get Aki's X11-free drawterm. A deal at twice the price!
next reply other threads:[~2006-12-24 5:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-24 5:26 ron minnich [this message]
2006-12-24 9:30 ` Richard Miller
2006-12-25 1:00 ` Jack Johnson
2006-12-24 10:25 ` Harri Haataja
2006-12-24 17:15 ` David Leimbach
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=13426df10612232126p669bd6eaq1411e0546c5dcd7@mail.gmail.com \
--to=rminnich@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).