| 1 |
Great idea! Often (espesially after a few days of inactivity) I don't |
| 2 |
have time to read all the threads and just delete the ones I'm not |
| 3 |
particularly interested in. However, you never know what a certain |
| 4 |
discussion might end up with. So I'd love to have a summary for those |
| 5 |
threads which actualy do end up with some decision. |
| 6 |
|
| 7 |
On Mon, 18 Aug 2003 16:24:36 -0400 |
| 8 |
Jason Wever <weeve@g.o> wrote: |
| 9 |
|
| 10 |
> Hi All, |
| 11 |
> |
| 12 |
> Since our -dev mailing list is now receiving an enormous amount of |
| 13 |
> traffic each day, I'd like to suggest bringing/bring back up the |
| 14 |
> summaries idea previously mentioned a few months ago. Due to the fact |
| 15 |
> that we all have limited time to work on Gentoo, and we can't spend |
| 16 |
> all of it reading the 50+ emails on -dev every day (not to mention |
| 17 |
> other list(s) we may be on).. So please, if a thread ends up resulting |
| 18 |
> in something devs need to read(i.e. policy changes), please make a |
| 19 |
> summary email. |
| 20 |
> |
| 21 |
> Also, for sparc, if you want us to test something, it is *HIGHLY |
| 22 |
> SUGGESTED* that you make a bug for it and CC the sparc team on it |
| 23 |
> <sparc@g.o>. As I've mentioned in the above paragraph about |
| 24 |
> email overload, it's easy for your test request to get lost in the |
| 25 |
> shuffle(especially if it's at the top of the 50+ emails to read). |
| 26 |
> This will guarantee the best response from the team. If you want to |
| 27 |
> do whatever with your ebuild(s) in the test request by a certain date, |
| 28 |
> please indicate that in the bug. |
| 29 |
> |
| 30 |
> Thanks, |
| 31 |
> -- |
| 32 |
> Jason Wever |
| 33 |
> Gentoo/Sparc Team Lead |
| 34 |
> |
| 35 |
|
| 36 |
|
| 37 |
-- |
| 38 |
Let the Force be with us! |
| 39 |
Sergey Kuleshov <svyatogor@g.o> |
| 40 |
Public Key: http://dev.gentoo.org/~sergey/gentoo-gpg |
Archives