From: Jeff Sickel <jas@corpus-callosum.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Mercurial and Plan 9
Date: Wed, 14 Mar 2012 01:28:48 -0500 [thread overview]
Message-ID: <8E336901-36C6-4A87-B957-AC839E0E7D02@corpus-callosum.com> (raw)
In-Reply-To: <CAGGHmKHPkNw5Sf5YfO7TkLVYrZLmbK7jj0nmd2osByyF9sYC2Q@mail.gmail.com>
On Mar 14, 2012, at 1:15 AM, Steven Stallion <sstallion@gmail.com> wrote:
>
> As for the current status, I'm working on a port for the latest stable
> (2.1.1 at the time of this writing). This should be complete soon -
> there are a few rough edges I want to polish first, particularly with
> documentation. This port should be a bit more complete than the last;
> I am aiming to have this become part of the official Mercurial
> distribution going forward.
That's great news.
> Jeff,
>
> I believe the biggest sore spot is the lack of a modern Python port.
> Ideally we could have a more complete port that wouldn't require APE,
> but that may be approaching the point of diminishing returns.
Do you see this as a potential GSoC effort? The sans-ape version,
build based off CPython 2.7 or 3.x? There are more dependencies
than just Python, but if we did have this updated then there would be
more opportunity for people to experiment with a Plan 9 system.
-jas
next prev parent reply other threads:[~2012-03-14 6:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-14 6:15 Steven Stallion
2012-03-14 6:28 ` Jeff Sickel [this message]
2012-03-14 15:17 ` Steven Stallion
2012-03-14 15:22 ` Yaroslav
2012-03-20 22:11 ` Federico Benavento
2013-01-04 21:56 ` Jeff Sickel
2013-01-04 23:10 ` Steven Stallion
2013-01-05 1:17 ` Charles Forsyth
2013-01-05 2:35 ` Federico G. Benavento
2013-01-07 15:13 ` Yaroslav
2012-03-14 9:19 ` Charles Forsyth
[not found] <CAGGHmKHPkNw5Sf5YfO7TkLVYrZLmbK7jj0nmd2osByyF9sYC2Q@mail.gmail.c>
2012-03-14 12:58 ` erik quanstrom
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=8E336901-36C6-4A87-B957-AC839E0E7D02@corpus-callosum.com \
--to=jas@corpus-callosum.com \
--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).