which patches to review

cgd@broadcom.com cgd@broadcom.com
Thu Apr 25 09:19:00 GMT 2002


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





More information about the Gdb-patches mailing list