From: Jeff Sickel <jas@corpus-callosum.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>,
nix-dev@googlegroups.com
Subject: [9fans] current python & hg support
Date: Thu, 9 Feb 2012 20:06:13 -0600 [thread overview]
Message-ID: <2002F9BB-6E50-47A0-8809-B01DAB4E2595@corpus-callosum.com> (raw)
A quick question for everyone, is there interest in getting a more current version of hg working for Plan 9 & NIX? If so, given I've spent way too much time in the past getting both working for other platforms, I could devote a little time to get both prepped for future work.
Python 2.5.1 is stable, but it wouldn't hurt us to be a little closer to the 2.7.1 release.
Hg has made significant strides since 1.0.2.
Neither of these updates might help the oddities people are finding while using Hg, but if we're looking forward then keeping current should be addressed.
-jas
next reply other threads:[~2012-02-10 2:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 2:06 Jeff Sickel [this message]
2012-02-10 3:33 ` Anthony Sorace
2012-02-10 5:03 ` John Floren
2012-02-10 5:55 ` Jens Staal
2012-02-10 6:43 ` erik quanstrom
2012-02-10 16:29 ` Jeff Sickel
2012-02-10 16:44 ` erik quanstrom
2012-02-10 17:03 ` John Floren
2012-02-10 17:50 ` Jeff Sickel
2012-02-11 11:43 ` Aram Hăvărneanu
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=2002F9BB-6E50-47A0-8809-B01DAB4E2595@corpus-callosum.com \
--to=jas@corpus-callosum.com \
--cc=9fans@9fans.net \
--cc=nix-dev@googlegroups.com \
/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).