From: Daniel Gryniewicz <dang@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] That time again...
Date: Fri, 27 Apr 2007 13:18:20 -0400 [thread overview]
Message-ID: <1177694300.29795.29.camel@athena.fprintf.net> (raw)
In-Reply-To: <20070426001201.GA21237@paradox.datanode.net>
On Wed, 2007-04-25 at 20:12 -0400, Michael Cummings wrote:
> Any other cool updates in the last few weeks? (it's been 20 days since
> the last time I started this thread - at this rate, we might make enough input
> to make Chris' job on the gwn easier).
>
For Gnome, 2.18.1 is almost entirely in the tree, but still masked
pending the unmasking of hal (which has one bug left, last I checked).
2.19.1 is going into the overlay slowly.
Daniel
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2007-04-27 17:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-26 0:12 [gentoo-dev] That time again Michael Cummings
2007-04-26 2:31 ` Paul Varner
2007-04-26 15:07 ` Christian Hartmann
2007-04-26 18:29 ` [gentoo-dev] " Christian Faulhammer
2007-04-30 19:17 ` Michael Cummings
2007-05-01 15:51 ` Alec Warner
2007-04-27 17:18 ` Daniel Gryniewicz [this message]
2007-04-27 17:45 ` [gentoo-dev] " Wernfried Haas
2007-04-27 18:54 ` Donnie Berkholz
2007-04-27 21:57 ` Donnie Berkholz
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=1177694300.29795.29.camel@athena.fprintf.net \
--to=dang@gentoo.org \
--cc=gentoo-dev@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