From: Lisa Seelye <lisa@gentoo.org>
To: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Cc: lisa@gentoo.org
Subject: [gentoo-dev] Should significant changes to arch be posted to -announce mail list?
Date: Fri, 03 Sep 2004 12:09:55 -0400 [thread overview]
Message-ID: <1094227795.20758.37.camel@lisa.thedoh.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 482 bytes --]
I think they should. Having new blockers come up on an arch box when
attempting to update is a little worrysome. Or having a new way of
doing things (such as the inevitable move to udev in lieu of devfs).
The things that I would hope to see in such an announcement would be a
suitable upgrade path, reason for change, and a link to gentoo-dev
discussion if available.
--
Regards,
Lisa Seelye
Key fingerprint = 09CF 52D6 B82B 72B9 97A7 601B CB46 B556 1E49 6FC5
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2004-09-03 16:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-03 16:09 Lisa Seelye [this message]
2004-09-03 16:14 ` [gentoo-dev] Should significant changes to arch be posted to -announce mail list? Ciaran McCreesh
2004-09-03 18:33 ` Lisa Seelye
2004-09-04 2:33 ` Lance Albertson
2004-09-05 3:51 ` Ned Ludd
2004-09-03 17:07 ` Kurt Lieber
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=1094227795.20758.37.camel@lisa.thedoh.com \
--to=lisa@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