9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Alexander Kapshuk <alexander.kapshuk@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] any git client?
Date: Wed,  6 Feb 2019 10:05:25 +0200	[thread overview]
Message-ID: <CAJ1xhMVQWVzvu6+-esvhNeWp0zW0V_OMm-RHzYxYuvT_6mNT-Q@mail.gmail.com> (raw)
In-Reply-To: <bd01932b28ccc1c7a61ad84d0f053a3d@hamnavoe.com>

On Mon, Feb 4, 2019 at 12:52 PM Richard Miller <9fans@hamnavoe.com> wrote:
>
> > to add to the last comment from skip, also note the availability of a
> > working ssh and sshfs on 9front :)
>
> Ssh also works fine on traditional plan9 if you apply these patches
> from http://9legacy.org/patch.html :
>         tls-devtls12.diff
>         tls-tlshand12.diff
>         libsec-x509-sha2.diff
>         libsec-tlshand12-nossl3.diff
>         libsec-tlshand12-norc4.diff
>         libsec-tlshand12-fixes.diff
>         libsec-x509-sig.diff
>
> These are already applied in the raspberry pi image:
>     http://9p.io/sources/contrib.miller/9pi.img.gz
>
>
How does one apply these patches?
By mounting http://9legacy.org/9legacy/patch on /n/sources/patch and
then using patch/apply? Or is there some other way?
Thanks.



  reply	other threads:[~2019-02-06  8:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-03 14:32 Mayuresh Kathe
2019-02-03 16:36 ` Chris McGee
2019-02-03 16:47   ` Steve Simon
2019-02-03 19:19   ` Sean Hinchee
2019-02-03 21:58     ` Ori Bernstein
2019-02-04  0:41 ` Skip Tavakkolian
2019-02-04  9:57   ` hiro
2019-02-04 10:50     ` Richard Miller
2019-02-06  8:05       ` Alexander Kapshuk [this message]
2019-02-06  9:43         ` Richard Miller
2019-02-06  9:47           ` Alexander Kapshuk
2019-02-05 10:42 ` Emery Hemingway
2019-02-07 13:59   ` Ethan Gardener
2019-02-07 18:26   ` Ori Bernstein

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=CAJ1xhMVQWVzvu6+-esvhNeWp0zW0V_OMm-RHzYxYuvT_6mNT-Q@mail.gmail.com \
    --to=alexander.kapshuk@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).