From: "Radoslaw Stachowiak" <radek@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] irregular metdata.xml check
Date: Sun, 27 May 2007 16:30:15 +0200 [thread overview]
Message-ID: <d25519e90705270730r385b154fob3fa7c99f4be540c@mail.gmail.com> (raw)
In-Reply-To: <200705271417.56549.bangert@gentoo.org>
On 27/05/07, Thilo Bangert <bangert@gentoo.org> wrote:
[...and many others...]
What I deeply miss from gentoo-dev mailing list is lack of summary at
end of discussions. Current situation is that at the end of such
disputes very often (of course not always :) is still unclear if:
* decision has been made (and what it is)
* previous approach has been changed (or it hasn't, with pointer (URL) to it)
* documents were updated (to address change or to simply provide
better wording) w/ URLs
* nothing has been changed due to X, and next approach will be in X months.
It's even more difficult to grasp outcome for non native english speakers.
Solution I propose is, that author of the first post in a thread, who
started the discussion (if there was some discusion), should at end of
it (let's assume it's 3 days after last mail) write summary with those
4 points I outlined above. Simple and will help greatly to track later
decisions/changes, or postponed items.
--
radoslaw.
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2007-05-27 14:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-23 17:49 [gentoo-dev] irregular metdata.xml check Thilo Bangert
2007-05-23 18:24 ` Chris Gianelloni
2007-05-23 18:34 ` [gentoo-dev] " Markus Ullmann
2007-05-23 19:01 ` [gentoo-dev] " Timothy Redaelli
2007-05-23 21:19 ` Robin H. Johnson
2007-05-27 12:17 ` Thilo Bangert
2007-05-27 14:30 ` Radoslaw Stachowiak [this message]
2007-06-10 20:58 ` [gentoo-dev] " Ryan Hill
2007-06-10 22:20 ` Robin H. Johnson
-- strict thread matches above, loose matches on Subject: below --
2007-06-10 23:41 [gentoo-dev] " Thilo Bangert
2007-06-11 5:55 ` Rémi Cardona
2007-06-11 8:20 ` Marijn Schouten (hkBst)
2007-06-11 8:26 ` Petteri Räty
2007-06-11 9:07 ` Robin H. Johnson
2007-06-11 16:34 ` Harald van Dijk
2009-12-07 11:56 Thilo Bangert
2009-12-07 12:13 ` Ulrich Mueller
2009-12-07 13:20 ` Thilo Bangert
2009-12-07 17:04 ` Hans de Graaff
2009-12-07 20:20 ` Thilo Bangert
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=d25519e90705270730r385b154fob3fa7c99f4be540c@mail.gmail.com \
--to=radek@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