9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Mistake in Plan9 Mercual port?
Date: Sat, 31 May 2014 12:55:21 -0400	[thread overview]
Message-ID: <95187ba31195b5bd7624f2c3a5524f8c@ladd.quanstro.net> (raw)
In-Reply-To: <CAGNd-2Pdjw0hkpZcTUqhVhRuNNeuQSQ5LiGHoYS3xjzBopiXMw@mail.gmail.com>

On Sat May 31 09:44:35 EDT 2014, pavel.klinkovsky@gmail.com wrote:

> Hi Steven,
>
> For the most part, using HTTP/S repositories will give you the best bang
> > for the proverbial buck.
>
>
> I see. In fact I tried to create and use Mercurial repository via 'ssh' and
> 'ftp' (via ftpfs) and none of them works.

jeff also did a port that supports 386 and amd64.  this is a key bit for me, since
i don't usually run a 386 or pae kernel.  and it may support arm (it did at one
point).  you can track the tip from jeff's repo.  (sadly they won't include proper plan 9 support.)
it does not use openssh, but sadly my copy at least also doesn't work with ssh2.  it gets
confused in authentication.

jeff: is this supposed to work?

jeff's version of python has fixed the bug where reads of a plan 9 device reporting
0 size always failed.

atta; hg version
Mercurial Distributed SCM (version 2.9.1)
(see http://mercurial.selenic.com for more information)

Copyright (C) 2005-2014 Matt Mackall and others
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
atta; python --version
Python 2.7.6
atta; echo $cputype
amd64

- erik



      parent reply	other threads:[~2014-05-31 16:55 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-31 12:41 Pavel Klinkovský
2014-05-31 12:52 ` Steven Stallion
2014-05-31 13:43   ` Pavel Klinkovský
2014-05-31 15:45     ` Jeff Sickel
2014-05-31 16:03       ` Aram Hăvărneanu
2014-05-31 16:17         ` Jeff Sickel
2014-05-31 16:20           ` Aram Hăvărneanu
2014-05-31 16:56             ` Jeff Sickel
2014-05-31 17:07               ` Aram Hăvărneanu
2014-05-31 18:10                 ` erik quanstrom
2014-05-31 22:03                   ` Steve Simon
2014-05-31 18:12                 ` Jeff Sickel
2014-05-31 18:26                   ` Aram Hăvărneanu
2014-05-31 18:37                     ` Jeff Sickel
2014-05-31 18:45                       ` Aram Hăvărneanu
2014-05-31 19:18                         ` Brian L. Stuart
2014-05-31 19:36                           ` Pavel Klinkovský
2014-06-01  5:48                             ` erik quanstrom
2014-06-01  7:45                               ` Pavel Klinkovský
2014-06-01 14:12                                 ` erik quanstrom
2014-06-01 14:46                                   ` Pavel Klinkovský
2014-06-01 14:54                                     ` erik quanstrom
2014-06-01 15:34                                     ` Jeff Sickel
2014-06-01 17:28                                       ` Pavel Klinkovský
2014-06-01  5:52         ` erik quanstrom
2014-05-31 16:55     ` erik quanstrom [this message]

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=95187ba31195b5bd7624f2c3a5524f8c@ladd.quanstro.net \
    --to=quanstro@quanstro.net \
    --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).