From: Steven Stallion <sstallion@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Mercurial and Plan 9
Date: Fri, 4 Jan 2013 15:10:26 -0800 [thread overview]
Message-ID: <CAGGHmKH0QYtMymcY3fXhgnBBzedMJZ2a-_xEp975HaWwDt2R0Q@mail.gmail.com> (raw)
In-Reply-To: <CEB385A1-F9B8-4EBF-A69D-BA37F6E384B7@corpus-callosum.com>
[-- Attachment #1: Type: text/plain, Size: 969 bytes --]
Hi Jeff,
Mercurial has been taken care of! I more or less track the latest stable
(stallion/mercurial). The existing Python port is sufficient for Mercurial,
though having a native Python port would be great. I've added Plan 9
support upstream in the Mercurial repository, so future builds are very
simple. In fact, it's even documented:
http://mercurial.selenic.com/wiki/Plan9FromBellLabs
Cheers,
Steve
On Fri, Jan 4, 2013 at 1:56 PM, Jeff Sickel <jas@corpus-callosum.com> wrote:
> Has anyone completed an APE lib sec yet?
>
> I'm starting to roll an ape build of libsec in as it's needed for
> a new Python 2.7.3+ port of Python. I'd gladly take someone else's
> mkfile rework to save some time. Libsec is needed to implement a
> new _hashlib module, one that doesn't require OpenSSL among others.
>
> The new Python release&build will be pushed out once I clean up
> a few more details like getting new builds of Mercurial working.
>
[-- Attachment #2: Type: text/html, Size: 1645 bytes --]
next prev parent reply other threads:[~2013-01-04 23:10 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
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 [this message]
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=CAGGHmKH0QYtMymcY3fXhgnBBzedMJZ2a-_xEp975HaWwDt2R0Q@mail.gmail.com \
--to=sstallion@gmail.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).