From: Dafydd Walters <dafydd@walters.net>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Gentoo Newsletter (Was: Ideas for user-developer communication)
Date: Thu, 21 Nov 2002 11:17:19 -0800 [thread overview]
Message-ID: <002101c29192$9c8ec450$550410ac@DWALTERS> (raw)
In-Reply-To: 200211211825.45798.danarmak@gentoo.org
> Ideally any developer (or user!) should write the editor(s) a quick note
> whenever he does something big and interesting in Gentoo. There might also
be
> some coverage of the Gentoo community itself, a la the kernel cousins -
such
> as summaries of important mailing list discussions. (Well, that's my own
> private idea, so ppl may disagree.)
I think harvesting the mailing lists for important discussions and
announcements is a good idea: Unfortunately, you can't always rely on
people being proactive in contacting editors with "big and interesting"
items.
--
gentoo-dev@gentoo.org mailing list
prev parent reply other threads:[~2002-11-21 19:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-16 21:09 [gentoo-dev] Ideas for user-developer communication oford
2002-11-18 18:06 ` Fred Van Andel
2002-11-21 16:25 ` [gentoo-dev] Gentoo Newsletter (Was: Ideas for user-developer communication) Dan Armak
2002-11-21 19:17 ` Dafydd Walters [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='002101c29192$9c8ec450$550410ac@DWALTERS' \
--to=dafydd@walters.net \
--cc=gentoo-dev@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