From: Jeremy Jackins <jeremyjackins@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Re: plan9port fossil
Date: Wed, 1 Apr 2020 18:23:19 -0700 [thread overview]
Message-ID: <CAOr72mgZMsZHVOqiTUgWODO6SrVyq2Zp0jCTQC4-Pkc3ooX7cQ@mail.gmail.com> (raw)
In-Reply-To: <CAOr72mgK4uLn40GexRdewQp8eyUGQvsjbFimFVpeeHXvQhBSbw@mail.gmail.com>
I hacked it a bit to make it work for me. I don't remember if there
was a problem with the normal setup or if I just wanted different
ergonomics.
https://gist.github.com/jnjackins/7228a9b2f3b2896cb379734605a34257
On Wed, 1 Apr 2020 at 17:59, Jeremy Jackins <jeremyjackins@gmail.com> wrote:
>
> It's not a patch or a fork, 0intro contributed it about 7 years ago:
> https://github.com/9fans/plan9port/tree/master/src/cmd/fossil
>
> I've used it and didn't run into any major issues. I recall attaching
> the console to e.g. /dev/tty8 for administration.
>
> On Wed, 1 Apr 2020 at 17:32, <cigar562hfsp952fans@icebubble.org> wrote:
> >
> > kim.lassila@gmail.com writes:
> >
> > > Does anyone run fossil from plan9port? Is it stable? I am thinking of
> > > setting up a fossil + venti fileserver on Linux that Plan 9 terminals
> > > and cpu servers can connect to.
> >
> > I don't think that plan9port includes a port of fossil. If anyone knows
> > of one (a patch, a fork, or whatever), please advise.
> >
> > ------------------------------------------
> > 9fans: 9fans
> > Permalink: https://9fans.topicbox.com/groups/9fans/T5df913730c26a8d5-Md2c0d4baf5bdc57c89126abf
> > Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2020-04-02 1:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-10 3:30 kim.lassila
2020-03-18 15:37 ` [9fans] " Steven Stallion
2020-03-19 12:34 ` Lucio De Re
2020-03-25 1:32 ` Plan9 on virtual machine in Mac os Mark Everett
2020-03-25 6:39 ` [9fans] " Cyber Fonic
2020-03-25 18:00 ` Ethan Gardener
2020-03-25 20:11 ` Brian L. Stuart
2020-03-25 22:17 ` Ethan Gardener
2020-03-25 6:44 ` Cyber Fonic
2020-03-25 21:35 ` Mark Everett
2020-03-25 21:43 ` Skip Tavakkolian
2020-03-25 10:04 ` Kim Lassila
2020-03-25 21:24 ` Skip Tavakkolian
2020-03-25 21:30 ` Nicolas S. Montanaro
2020-03-25 22:21 ` Ethan Gardener
2020-04-02 12:09 ` [9fans] plan9port fossil Ole-Hjalmar Kristensen
2020-04-02 13:37 ` Lucio De Re
2020-03-20 3:41 ` Kim Lassila
2020-04-01 23:52 ` cigar562hfsp952fans
2020-04-02 0:59 ` [9fans] " Jeremy Jackins
2020-04-02 1:23 ` Jeremy Jackins [this message]
2020-04-04 13:45 ` [9fans] " Kim Lassila
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=CAOr72mgZMsZHVOqiTUgWODO6SrVyq2Zp0jCTQC4-Pkc3ooX7cQ@mail.gmail.com \
--to=jeremyjackins@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).