From: "David Leimbach" <leimy2k@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] why I'm messing with python: mercurial
Date: Sun, 24 Dec 2006 09:15:55 -0800 [thread overview]
Message-ID: <3e1162e60612240915t2e2e53a4qfef352ebeb867303@mail.gmail.com> (raw)
In-Reply-To: <20061224102511.GA13434@XTL.antioffline.net>
On 12/24/06, Harri Haataja <harriha@mail.student.oulu.fi> wrote:
> On Sat, Dec 23, 2006 at 10:26:07PM -0700, ron minnich wrote:
> > 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.
>
> My vote would go to darcs, but I think that the GHC runtime is quite far
> away :)
>
I'd like GHC on Plan 9 quite a bit by itself,
prev parent reply other threads:[~2006-12-24 17:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-24 5:26 ron minnich
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 [this message]
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=3e1162e60612240915t2e2e53a4qfef352ebeb867303@mail.gmail.com \
--to=leimy2k@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).