From: Douglas Campos <qmx2352@gmail.com>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] moving uClibc 0.9.28 to stable
Date: Wed, 25 Jan 2006 08:38:04 -0200 [thread overview]
Message-ID: <cc04c5eb0601250238u61b482aau64348451e748ae19@mail.gmail.com> (raw)
In-Reply-To: <200601231824.52701.vapier@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 445 bytes --]
Very neat!
Thanx
On 1/23/06, Mike Frysinger <vapier@gentoo.org> wrote:
>
> On Monday 23 January 2006 17:53, René Rhéaume wrote:
> > 2006/1/23, Mike Frysinger <vapier@gentoo.org>:
> > > planning on doing this wed nite (Jan/25)
> >
> > Will updated embedded stage be available on 2006.0 release?
>
> of course
>
> i already have most built on my local machines
> -mike
>
> --
> gentoo-embedded@gentoo.org mailing list
>
>
[-- Attachment #2: Type: text/html, Size: 858 bytes --]
prev parent reply other threads:[~2006-01-25 10:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-23 22:42 [gentoo-embedded] moving uClibc 0.9.28 to stable Mike Frysinger
2006-01-23 22:53 ` René Rhéaume
2006-01-23 23:24 ` Mike Frysinger
2006-01-25 10:38 ` Douglas Campos [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=cc04c5eb0601250238u61b482aau64348451e748ae19@mail.gmail.com \
--to=qmx2352@gmail.com \
--cc=gentoo-embedded@lists.gentoo.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