From: George Shapovalov <george@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Misquoted in the GWN
Date: Mon, 28 Nov 2005 12:46:47 +0100 [thread overview]
Message-ID: <200511281246.48125.george@gentoo.org> (raw)
In-Reply-To: <438AEA54.40107@gentoo.org>
On Monday, 28. November 2005 12.30, Simon Stelling wrote:
> Is there a good reason for sending this to -dev?
Because he wanted to let users know of corrections? At least the ones who
care.
As for the original issue, isn't this the policy and how it has always been in
fact? Back in earlier days (in just early days we did not have GWN :))
everybody that I know of was contacted, well I even so pings on -dev by GWN
people asking for an "interview" :).
George
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-11-28 11:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-28 9:48 [gentoo-dev] Misquoted in the GWN Henrik Brix Andersen
2005-11-28 11:30 ` Simon Stelling
2005-11-28 11:46 ` George Shapovalov [this message]
2005-11-28 11:54 ` Henrik Brix Andersen
2005-11-28 17:54 ` Ciaran McCreesh
2005-11-28 18:46 ` Patrick Lauer
2005-11-28 18:54 ` Ciaran McCreesh
2005-11-28 19:42 ` Grobian
2005-11-28 18:59 ` Lance Albertson
2005-11-28 19:00 ` Stephen P. Becker
2005-11-28 19:05 ` Jeroen Roovers
2005-11-28 19:19 ` Grant Goodyear
2005-11-29 13:03 ` [gentoo-dev] " Duncan
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=200511281246.48125.george@gentoo.org \
--to=george@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