From: Tony Mendoza <clueelf@tonymendoza.us>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] 9front, git and mercurial.
Date: Mon, 14 Jun 2021 12:48:35 -0500 [thread overview]
Message-ID: <96700b75f4544cca03f13fd1c84d8003@smtp.hushmail.com> (raw)
In-Reply-To: <ECEA7C9E140FA97F7191F934D0E0CCF8@eigenstate.org>
Quick question (or maybe not), but how are these being hosted? Is this done on a cloud provider vm platform? Or is this being done in a traditional DC using real hardware?
Just curious to know how this is being done because I would like to do something similar.
Cheers!
Tony
—
Tony Mendoza
clueelf@tonymendoza.us
> On Jun 13, 2021, at 7:48 PM, ori@eigenstate.org wrote:
>
> Posting here for wider distribution:
>
> 9front is fully self-hosting on git, running the
> git-server for 9front on 9front. So, hg and python
> are now removed from the distribution, but will be
> archived here:
>
> git://git.9front.org/plan9front/pyhg
>
> After a sysupdate, you'll probably want
> to clean up the remaining bits of python:
>
> rm /$objtype/bin/python
> cd /sys/man && mk
>
> Also, in case anyone in the 9legacy world
> was using git9: look for the most recent
> version in:
>
> /sys/src/cmd/git
>
> or on the web at:
>
> http://git.9front.org/plan9front/plan9front/HEAD/sys/src/cmd/git/f.html
>
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T7dfa66085e395bcb-Ma3ff99cd9f31645125d9f0c1
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2021-06-14 17:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-14 0:47 ori
2021-06-14 17:48 ` Tony Mendoza [this message]
2021-06-14 17:55 ` Kurt H Maier
2021-06-14 19:13 ` ori
2022-05-18 18:12 ` Frank D. Engel, Jr.
2022-05-18 18:30 ` Kurt H Maier via 9fans
2022-05-18 19:41 ` Frank D. Engel, Jr.
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=96700b75f4544cca03f13fd1c84d8003@smtp.hushmail.com \
--to=clueelf@tonymendoza.us \
--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).