From: Fred Van Andel <fred@vanandel.net>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Ideas for user-developer communication
Date: Mon, 18 Nov 2002 10:06:43 -0800 [thread overview]
Message-ID: <20021118100643.5A15C340.fred@vanandel.net> (raw)
In-Reply-To: <1037480947.13270.2.camel@beige>
oford <oford@ev1.net> wrote:
(11/16/2002 13:09)
>
>
>>I also remember a weekly newsdigest being discussed on core, afaicr all
>>response to that was positive. It hasn't seen the daylight yet, but i
>>think that's because the devs are usually quite busy doing stuff not
>>thinking about/having the time to put such a mailing together. Maybe an
>>idea to assign it to the doc team or a (group of) helpful users ?
>>
>>- foser
>
>Helpful user reporting for duty. If we can get more than one it will be
>much easier though.
>
>
>Owen Ford
You have more than one now. Shall we go for more that two?
Fred Van Andel
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2002-11-18 18:07 UTC|newest]
Thread overview: 19+ 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 [this message]
2002-11-21 16:25 ` [gentoo-dev] Gentoo Newsletter (Was: Ideas for user-developer communication) Dan Armak
2002-11-21 19:17 ` Dafydd Walters
-- strict thread matches above, loose matches on Subject: below --
2002-11-18 20:06 [gentoo-dev] Ideas for user-developer communication Sean P. Kane
2002-11-18 22:57 ` Spider
2002-11-18 16:25 Sean P. Kane
2002-11-18 17:44 ` Ahmed Bouagja
2002-11-18 19:32 ` Christian Skarby
2002-11-15 23:44 Jyrinx
2002-11-16 1:30 ` Antoine Jacoutot
2002-11-16 16:53 ` Spider
2002-11-16 17:45 ` foser
2002-11-16 17:51 ` Bart Verwilst
2002-11-16 18:26 ` Spider
2002-11-16 18:34 ` foser
2002-11-17 1:17 ` Spider
2002-11-17 7:02 ` Mark Constable
2002-11-17 12:53 ` Spider
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=20021118100643.5A15C340.fred@vanandel.net \
--to=fred@vanandel.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