To: 9front@9front.org
Subject: Re: [9front] Hello everybody!From: Michal Bien <glorfdev@gmail.com>
Date: Sun, 17 Feb 2013 22:44:11 +0100 [thread overview]
Message-ID: <CAGSv20rO=x1CCABQUgqJGLYP4hGc8FQyMpD5G__bj5KDspr28A@mail.gmail.com> (raw)
In-Reply-To: <360c75416118af0e04904ea65c8ca86f@9front.org>
[-- Attachment #1: Type: text/plain, Size: 331 bytes --]
Yes, of course, and it works without problems on sabertooth 990fx! (with
kernel patched only for ethernet).
2013/2/17 <sl@9front.org>
> > I've never known about plan9front, but now, I want to help improve it.
> > So first question, how to publish to plan9front hg?
>
> Hello Michal.
>
> Have you installed 9front yet?
>
> -sl
>
[-- Attachment #2: Type: text/html, Size: 686 bytes --]
prev parent reply other threads:[~2013-02-17 21:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-17 19:08 Hello everybody!From: Plan9 Maniac <glorfdev@gmail.com>
2013-02-17 19:23 ` [9front] Hello everybody!In-Reply-To: <CAGSv20oGmxHevwx2Lp4k-NmGCtMS83qhgHUUsKFxmWfqhTOxOw@mail.gmail.com> sl
2013-02-17 21:44 ` [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='CAGSv20rO=x1CCABQUgqJGLYP4hGc8FQyMpD5G__bj5KDspr28A@mail.gmail.com' \
--to=9front@9front.org \
/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).