From: "Tony \"Chainsaw\" Vroon" <chainsaw@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: council@gentoo.org
Subject: Re: [gentoo-dev] >= udev-182 tracker
Date: Wed, 11 Apr 2012 22:20:35 +0100 [thread overview]
Message-ID: <1334179235.8733.30.camel@localhost> (raw)
In-Reply-To: <20120411195345.GA19071@linux1>
[-- Attachment #1: Type: text/plain, Size: 275 bytes --]
On Wed, 2012-04-11 at 14:53 -0500, William Hubbs wrote:
> Does this answer any fears about trying to force an untimely
> stabilization?
It certainly helps me sleep at night, yes. Any... inconveniences forced
on me have to be fixed over 40 times.
Regards,
Tony V.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2012-04-11 21:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-11 19:53 [gentoo-dev] >= udev-182 tracker William Hubbs
2012-04-11 19:58 ` 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 [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=1334179235.8733.30.camel@localhost \
--to=chainsaw@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