[BusyBox] [PATCH] ASH's read bugs

Paul Fox pgf at brightstareng.com
Thu Sep 8 13:01:35 UTC 2005


 > > i've committed the patch from bug 242 to svn, which independently
 > > (of this mail and bug 348) addressed the '-t timeout" bugs, and
 > > added "-n nchars" functionality.  based on bug 348 and this mail,
 > > i also added "-s", for silent reads.
 > >
 > > paul
 > 
 > Would someone please explain to me the difference between "resolved" and 
 > "closed" as used in our current bug system?  (Resolved is a bit like zombie 
 > processes, isn't it?)
 > 
 > 242 is "resolved", but 348 is "closed".  Resolved still shows up in the list 
 > by default, closed doesn't unless you ask for it...

what i've been doing, is mainly "resolving", except in the case of
really obvious things like 348, which was a dup of 242, so i
"closed" it.  i've been using "resolve" so that people get a chance
to see what was done, before the bug disappears from view
entirely.  at some point when i did my first pass throught the
old bugs, i was doing this, and erik came along a week or so
later and changed all the "resolved" bugs to "closed".  taking
that as positive feedback, i continued doing things that way,
figuring that he, at least, wanted to see what was being done.

but, like, rob, i'd like to hear consensus on how to use the
system so that everyone gets what they need.  erik?  bueller? 
thoughts?

if it could be automated, i'd vote for manually "resolving", and
having cron do a nightly "resolved --> closed" on anything that
had been in resolved state for more than a few days.  i'd guess
that's not possible, though.

paul
=---------------------
 paul fox, pgf at brightstareng.com



More information about the busybox mailing list