From: Eli Zaretskii <eliz@elta.co.il>
To: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
Cc: cagney@gnu.org,gdb@sources.redhat.com
Subject: Re: Close all [most] SPARC PRs?
Date: Thu, 19 Feb 2004 05:53:00 -0000 [thread overview]
Message-ID: <u3c97k428.fsf@elta.co.il> (raw)
In-Reply-To: <20040218214740.D8E584B367@berman.michael-chastain.com> (mec.gnu@mindspring.com)
> Date: Wed, 18 Feb 2004 16:47:40 -0500 (EST)
> From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
>
> Attach that message in a change from "open" -> "feedback".
> Wait 30 days.
>
> About 80% of cases, nothing happens for 30 days. Then close the PR,
> with another little note: "I haven't heard anything for 30 days.
> I am closing the PR. If you have problems with a more recent version
> of gdb, please file another PR."
>
> About 15% of cases, the original submitter writes back sooner and
> confirms that the original bug is closed. Then close the PR.
>
> About 5% of cases, the original submitter says something which indicates
> that we shouldn't close the PR.
>
> Mark K already did a 30-day routine on a bunch of Solaris PR's,
> and the 30 days ran out, and he closed the PR's.
>
> Anyways, that's how I like to do it.
I really like this procedure. Blindly closing the PRs should not be
our first choice if we can do better, and what Michael suggests _is_,
IMHO, better.
next prev parent reply other threads:[~2004-02-19 5:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-18 21:48 Michael Elizabeth Chastain
2004-02-19 5:53 ` Eli Zaretskii [this message]
2004-02-20 16:55 ` Andrew Cagney
2004-02-20 17:57 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2004-02-20 18:10 Michael Elizabeth Chastain
2004-02-20 18:27 ` Andrew Cagney
2004-02-18 20:18 Andrew Cagney
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=u3c97k428.fsf@elta.co.il \
--to=eliz@elta.co.il \
--cc=cagney@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=mec.gnu@mindspring.com \
/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