From: Steven Stallion <sstallion@gmail.com>
To: 9fans@9fans.net
Subject: [9fans] Mercurial and Plan 9
Date: Tue, 13 Mar 2012 23:15:18 -0700 [thread overview]
Message-ID: <CAGGHmKHPkNw5Sf5YfO7TkLVYrZLmbK7jj0nmd2osByyF9sYC2Q@mail.gmail.com> (raw)
All,
I have to admit I've been a bit late posting to the list regarding
updates to Mercurial. As Erik has mentioned a couple of times, a 1.7.5
port was made last year (a factotum extension for http/https
authentication was also written; see
/n/sources/contrib/stallion/src/mercurial). This port has seen heavy
use over the last year with a fair degree of success - I am finally
comfortable making this a bit more public. stallion/mercurial is
available via fgb's contrib. You will want to check
/n/sources/contrib/stallion/src/mercurial/README before installing.
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.
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.
Cheers,
Steve
next reply other threads:[~2012-03-14 6:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-14 6:15 Steven Stallion [this message]
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
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=CAGGHmKHPkNw5Sf5YfO7TkLVYrZLmbK7jj0nmd2osByyF9sYC2Q@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).