From: Stanley Lieber <firstname.lastname@example.org>
Subject: Re: [9front] Introduction and regarding guidance
Date: Thu, 2 Jun 2022 10:50:26 -0400 [thread overview]
Message-ID: <D37D0FF5-1D93-42CD-B535-0770E47F4CE3@stanleylieber.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1381 bytes --]
if you’ve already installed you already have all teh source code in /sys/src/ on your installed system.
9front’s source moved from hg to git. it’s now located here:
> On Jun 2, 2022, at 10:48 AM, Deepak kr. Mahato <Deepakkrmahato@proton.me> wrote:
> Hey Ori, Thanks for the reply, uptill now I am able to set up 9front on Virtual Environment and introducing myself to it.
> What i am having difficulty is getting the source code on my PC,
> the `hg clone http://code.9front.org/hg/plan9front` command is giving me
> `abort: error: Connection timed out`
> I am clueless to how to proceed.
> Sent with Proton Mail secure email.
> ------- Original Message -------
>> On Thursday, June 2nd, 2022 at 4:13 AM, <email@example.com> wrote:
>> Quoth Deepak kr. Mahato Deepakkrmahato@proton.me:
>>> Could anyone please guide me in what other concepts I should start looking
>>> into and how do I familiarize myself with 9front and get started in working
>>> with its codebase so that I may be able to make valuable contributions.
>> use it and fix the stuff that annoys you.
>> there's nobody here to tell you want to work on; this is
>> your hobby, you get to decide how you go about it.
>> there are some old gsoc idea lists, I guess.
[-- Attachment #2: Type: text/html, Size: 2802 bytes --]
next prev parent reply other threads:[~2022-06-02 14:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 20:36 Deepak kr. Mahato
2022-06-01 22:43 ` ori
2022-06-02 0:27 ` Frank D. Engel, Jr.
2022-06-02 1:54 ` Noam Preil
2022-06-02 3:05 ` sirjofri
2022-06-02 3:21 ` noam
2022-06-02 4:22 ` william
2022-06-02 4:55 ` Mart Zirnask
2022-06-02 5:02 ` sirjofri
2022-06-02 14:44 ` Deepak kr. Mahato
2022-06-02 14:50 ` Stanley Lieber [this message]
2022-06-02 14:51 ` Christos Margiolis
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).