From: Svyatogor <svyatogor@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Email Overload; Make summaries and bugs for test requests
Date: Tue, 19 Aug 2003 11:03:55 +0300 [thread overview]
Message-ID: <20030819110355.3730ba1f.svyatogor@gentoo.org> (raw)
In-Reply-To: <20030818162436.2863ef2d.weeve@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1632 bytes --]
Great idea! Often (espesially after a few days of inactivity) I don't
have time to read all the threads and just delete the ones I'm not
particularly interested in. However, you never know what a certain
discussion might end up with. So I'd love to have a summary for those
threads which actualy do end up with some decision.
On Mon, 18 Aug 2003 16:24:36 -0400
Jason Wever <weeve@gentoo.org> wrote:
> Hi All,
>
> Since our -dev mailing list is now receiving an enormous amount of
> traffic each day, I'd like to suggest bringing/bring back up the
> summaries idea previously mentioned a few months ago. Due to the fact
> that we all have limited time to work on Gentoo, and we can't spend
> all of it reading the 50+ emails on -dev every day (not to mention
> other list(s) we may be on).. So please, if a thread ends up resulting
> in something devs need to read(i.e. policy changes), please make a
> summary email.
>
> Also, for sparc, if you want us to test something, it is *HIGHLY
> SUGGESTED* that you make a bug for it and CC the sparc team on it
> <sparc@gentoo.org>. As I've mentioned in the above paragraph about
> email overload, it's easy for your test request to get lost in the
> shuffle(especially if it's at the top of the 50+ emails to read).
> This will guarantee the best response from the team. If you want to
> do whatever with your ebuild(s) in the test request by a certain date,
> please indicate that in the bug.
>
> Thanks,
> --
> Jason Wever
> Gentoo/Sparc Team Lead
>
--
Let the Force be with us!
Sergey Kuleshov <svyatogor@gentoo.org>
Public Key: http://dev.gentoo.org/~sergey/gentoo-gpg
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-08-19 7:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-18 20:24 [gentoo-dev] Email Overload; Make summaries and bugs for test requests Jason Wever
2003-08-19 8:03 ` Svyatogor [this message]
2003-08-19 11:34 ` Chris Gianelloni
2003-08-27 9:40 ` Svyatogor
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=20030819110355.3730ba1f.svyatogor@gentoo.org \
--to=svyatogor@gentoo.org \
--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