From: David Leimbach <leimy2k@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Mercurial port is official
Date: Fri, 27 Apr 2012 08:50:03 -0700 [thread overview]
Message-ID: <CAJJ04x5uMFqNW5=sbP+QTjJvZJqkpgZ6rp7qWxCVRCMFa+cfAA@mail.gmail.com> (raw)
In-Reply-To: <CAGGHmKHuG32-SKS8YGYg9M6RHm7eDiJe=h=pjC8xnRm__vyj9w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1350 bytes --]
This is truly excellent.
Now to get Python to work out of the box on Plan 9.
Dave
On Fri, Apr 27, 2012 at 8:04 AM, Steven Stallion <sstallion@gmail.com>wrote:
> All,
>
> I'm happy to report that the official Mecurial port is complete and
> has been accepted upstream. Starting with version 2.2, Mercurial will
> support Plan 9 and friends out of the box.
>
> You can find more information about the port here:
>
> http://mercurial.selenic.com/wiki/Plan9FromBellLabs
> http://mercurial.selenic.com/wiki/FactotumExtension
>
> I've updated stallion/mercurial to version 2.2-rc for the time being.
> The official 2.2 release is scheduled for the first of May. As soon as
> the release is made, I'll update the package.
>
> Some (slightly) bad news:
>
> Due to the number of changes that needed to be made in order for the
> port to be accepted upstream, I decided to recreate the contrib
> package. If you have installed a previous revision of
> stallion/mercurial, please be sure to completely remove it before
> installing the new one. Installation is slightly manual since it
> requires removing incorrect paths that were installed by
> bichued/python, however the process is documented in the
> Plan9FromBellLabs page above and in
> sources/contrib/stallion/src/mercurial/README.
>
> Cheers,
>
> Steve
>
>
[-- Attachment #2: Type: text/html, Size: 1996 bytes --]
next prev parent reply other threads:[~2012-04-27 15:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-27 15:04 Steven Stallion
2012-04-27 15:50 ` David Leimbach [this message]
2012-04-27 16:11 ` Aram Hăvărneanu
2012-04-27 16:31 ` Yaroslav
2012-04-27 16:40 ` balaji
2012-04-27 18:44 ` Steven Stallion
2012-04-27 16:45 ` Jens Staal
2012-04-27 18:46 ` Steven Stallion
2012-05-02 0:52 ` Steven Stallion
2012-05-04 1:04 ` Akshat Kumar
2012-05-04 3:08 ` Steven Stallion
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='CAJJ04x5uMFqNW5=sbP+QTjJvZJqkpgZ6rp7qWxCVRCMFa+cfAA@mail.gmail.com' \
--to=leimy2k@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).