From: Joost Roeleveld <joost@antarean.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Will the next auto-build stage tar ball include OpenRC update?
Date: Thu, 12 May 2011 14:30:51 +0200 [thread overview]
Message-ID: <3853574.JxeBK68k1L@eve> (raw)
In-Reply-To: <BANLkTi=FoFXtZt2xZA34K2GCt_8uGYWy0g@mail.gmail.com>
On Thursday 12 May 2011 17:12:30 dong l wrote:
> 个人经历，baselayout的更新其实都不怎么suffer,呵呵～
huh?
>
> 2011/5/12 刘勇泰 <lytive@gmail.com>:
> > Hello everyone. I am going to build a new gentoo box. Will the next
> > auto-build stage tar ball (2011-5-12) for amd64 include the OpenRC
> > update? If so I will not suffer the baselayout updating.
next prev parent reply other threads:[~2011-05-12 12:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-12 3:48 [gentoo-user] Will the next auto-build stage tar ball include OpenRC update? 刘勇泰
2011-05-12 9:12 ` dong l
2011-05-12 12:30 ` Joost Roeleveld [this message]
2011-05-12 13:03 ` Dale
2011-05-12 13:32 ` Xiangru Chen
2011-05-12 23:10 ` [gentoo-user] " masterprometheus
[not found] <gRve9-4ir-1@gated-at.bofh.it>
[not found] ` <gRAdQ-4A0-11@gated-at.bofh.it>
[not found] ` <gRDlo-1md-3@gated-at.bofh.it>
2011-05-12 12:43 ` [gentoo-user] " Indi
2011-05-12 14:00 ` Thanasis
2011-05-13 1:27 ` 刘勇泰
2011-05-13 1:48 ` Mike Edenfield
2011-05-13 1:26 ` 刘勇泰
[not found] <gRDv4-1Ar-11@gated-at.bofh.it>
[not found] ` <gRDv4-1Ar-13@gated-at.bofh.it>
[not found] ` <gRDv4-1Ar-15@gated-at.bofh.it>
[not found] ` <gRDv4-1Ar-9@gated-at.bofh.it>
[not found] ` <gREKu-3To-53@gated-at.bofh.it>
[not found] ` <gRPwd-54j-5@gated-at.bofh.it>
2011-05-13 1:54 ` Indi
2011-05-13 13:22 ` Joost Roeleveld
2011-05-13 15:33 ` Blackdream W
2011-05-13 15:45 ` dong l
2011-05-13 17:24 ` Joost Roeleveld
2011-05-13 15:47 ` Joost Roeleveld
-- strict thread matches above, loose matches on Subject: below --
2011-05-13 16:04 Blackdream W
2011-05-13 17:25 ` Joost Roeleveld
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=3853574.JxeBK68k1L@eve \
--to=joost@antarean.org \
--cc=gentoo-user@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