From: "Carlos O'Donell" <carlos@systemhalted.org>
To: Andreas Grapentin <andreas@grapentin.org>
Cc: libc-ports@sourceware.org
Subject: Re: port to minix3
Date: Fri, 14 Dec 2012 16:01:00 -0000 [thread overview]
Message-ID: <CAE2sS1j_3pPnKai==VMgG-bHm5MbO7fXmPP385EUn7i5H4SiZA@mail.gmail.com> (raw)
In-Reply-To: <50CB3D25.9070809@grapentin.org>
On Fri, Dec 14, 2012 at 9:52 AM, Andreas Grapentin
<andreas@grapentin.org> wrote:
> hi,
>
> I need a port of glibc to Minix 3.2 and decided to do it myself.
> I'll be following this guide:
> http://www.gnu.org/software/libc/manual/html_node/Porting.html
>
> and I'll let you know if there is any progress at all :)
Get involved, ask questions, and feel free to post early snapshots for review.
Welcome to the community!
Cheers,
Carlos.
next prev parent reply other threads:[~2012-12-14 16:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-14 14:53 Andreas Grapentin
2012-12-14 15:44 ` Игорь Пашев
2012-12-14 16:01 ` Carlos O'Donell [this message]
2012-12-16 17:12 ` Andreas Grapentin
2012-12-16 17:51 ` Игорь Пашев
2012-12-15 11:53 ` Thomas Schwinge
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='CAE2sS1j_3pPnKai==VMgG-bHm5MbO7fXmPP385EUn7i5H4SiZA@mail.gmail.com' \
--to=carlos@systemhalted.org \
--cc=andreas@grapentin.org \
--cc=libc-ports@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).