From: Steven Stallion <sstallion@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 11:44:24 -0700 [thread overview]
Message-ID: <CAGGHmKFyf2ZtsTOEDoL09ErHBGhSfm5-hRneS+gKMM+-KNgJhQ@mail.gmail.com> (raw)
In-Reply-To: <CANE8Qwewboq9CHqeXH1zdMXf8ZpSR8kD=vnU+3arcfkzpT0jbg@mail.gmail.com>
On Fri, Apr 27, 2012 at 9:40 AM, balaji
<balaji.srinivasa+plan9@gmail.com> wrote:
> This is great news. Bichued fixed some of fgb's intial port work to
> make it work on plan9.
> If i'm not mistaken its to do with threading etc, but it was working
> well, including hgweb.
> I'm curious to know (ofcourse without reading the links sent below) if
> it supports https/ssh based checkin/checkouts.
> This was one reason why we could not use it in a public environment.
Hi Bal,
HTTP/HTTPS should work without any problems (we've been using it for
the last year and a half or so on older versions of Mercurial with no
problems). SSH is a bit tougher. Mercurial assumes that OpenSSH is
installed on the system. Unfortunately, even if the openssh package is
installed there were a couple of problems we came across in Python
itself in the pipe handling.
Anecdotally speaking, Mercurial has been much more pleasant over HTTP
- we haven't looked back since moving our repositories over. To reduce
some of the pain, use of the scheme extension allows us to shorten up
the repository URLs:
hg clone hg://src/someproject
In /lib/mercurial/hgrc:
[schemes]
hg = https://hg.mysite.com/
Cheers,
Steve
next prev parent reply other threads:[~2012-04-27 18:44 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
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 [this message]
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=CAGGHmKFyf2ZtsTOEDoL09ErHBGhSfm5-hRneS+gKMM+-KNgJhQ@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).