From: cgd@broadcom.com
To: ac131313@cygnus.com
Cc: "David S. Miller" <davem@redhat.com>,
kevinb@redhat.com, shebs@apple.com, drow@mvista.com,
gdb-patches@sources.redhat.com
Subject: Re: which patches to review
Date: Thu, 25 Apr 2002 09:19:00 -0000 [thread overview]
Message-ID: <yov51yd3vjjd.fsf@broadcom.com> (raw)
In-Reply-To: ac131313@cygnus.com's message of "Thu, 25 Apr 2002 14:04:30 +0000 (UTC)"
At Thu, 25 Apr 2002 14:04:30 +0000 (UTC), "Andrew Cagney" wrote:
> David, to (possibly re-iterate) some previous suggestions:
>
> > If you post a new patch, start a new thread.
> > If you superseed a patch, clearly withdraw the old patch.
>
> This makes life easier for everyone and is accepted pratice on this list.
My personal practice, which i've found helpful in the past, is to keep
a list of patches i've submitted, keep track of their status, and
occasionally send a ping msg containing the list of unreviewed patches
that have gone "too long" w/o approval or rejection.
Like it or not, even in the best circumstances things _do_ get lost,
dropped, overlooked, or otherwise ignored occasionally. That's
especially true when volunteers are doing the reviewing, and the
volunteers are busy.
I've found that it also helps me keep track of my own outstanding
patches when _I_ get really busy and distracted for a month at a
time... 8-)
(my personal cutoff for 'too long' tends to be '2 weeks to a month, or
whenever after a longer period i remember to look at my outstanding
patches page.' 8-)
chris
next prev parent reply other threads:[~2002-04-25 16:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-22 22:49 David S. Miller
2002-04-23 7:47 ` Elena Zannoni
2002-04-23 7:54 ` Daniel Jacobowitz
2002-04-23 22:19 ` David S. Miller
2002-04-24 8:53 ` Stan Shebs
2002-04-24 10:16 ` Andrew Cagney
2002-04-24 10:48 ` David S. Miller
2002-04-24 12:16 ` Kevin Buettner
2002-04-24 12:25 ` David S. Miller
2002-04-25 7:04 ` Andrew Cagney
[not found] ` <mailpost.1019743470.13502@news-sj1-1>
2002-04-25 9:19 ` cgd [this message]
2002-04-25 7:32 ` Andrew Cagney
2002-04-25 18:04 ` David S. Miller
2002-04-25 20:27 ` Andrew Cagney
2002-04-25 18:14 ` Daniel Jacobowitz
2002-04-25 18:36 ` Christopher Faylor
2002-04-25 18:45 ` Daniel Jacobowitz
2002-04-25 19:17 ` Christopher Faylor
2002-04-25 20:33 ` Andrew Cagney
2002-04-26 9:26 ` Stan Shebs
2002-04-25 20:17 ` Andrew Cagney
2002-04-25 22:00 ` Daniel Jacobowitz
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=yov51yd3vjjd.fsf@broadcom.com \
--to=cgd@broadcom.com \
--cc=ac131313@cygnus.com \
--cc=davem@redhat.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kevinb@redhat.com \
--cc=shebs@apple.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