From: William Hubbs <williamh@gentoo.org>
To: gentoo development <gentoo-dev@lists.gentoo.org>
Cc: council@gentoo.org
Subject: [gentoo-dev] >= udev-182 tracker
Date: Wed, 11 Apr 2012 14:53:45 -0500 [thread overview]
Message-ID: <20120411195345.GA19071@linux1> (raw)
[-- Attachment #1: Type: text/plain, Size: 607 bytes --]
All,
here is what I see on the current udev situation:
The council has made a decision that we will continue supporting
split out /usr.
This, however, was never in question. No one is planning to drop support
for separate /usr. Also, no one is planning on trying to force
stabilize udev-182 within 30 days.
To allay any fears of that happening, I have opened a tracker [1] for
issues which need to be resolved before newer udevs can go stable.
Does this answer any fears about trying to force an untimely
stabilization?
William
[1] https://bugs.gentoo.org/show_bug.cgi?id=411627
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2012-04-11 19:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-11 19:53 William Hubbs [this message]
2012-04-11 19:58 ` [gentoo-dev] >= udev-182 tracker Michał Górny
2012-04-11 20:10 ` William Hubbs
2012-04-11 21:53 ` Alec Warner
2012-04-11 23:00 ` Alexandre Rostovtsev
2012-04-11 20:01 ` Rich Freeman
2012-04-11 21:20 ` Tony "Chainsaw" Vroon
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=20120411195345.GA19071@linux1 \
--to=williamh@gentoo.org \
--cc=council@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