Earnie Boyd wrote on Thursday, December 07, 2000:
EB> --- Paul Garceau <pgarceau@...> wrote:
>> Hi folks,
>> What does everyone think about sending all patch related stuff
>> to mingw-patches@...?
>> That would mean that any patch updates, new patches,
>> discussions of patches, etc. would all go to that mailing list.
>> Looking forward to hearing from everyone.
EB> It would be my preference. The SourceForge Patch Manager could be used as a
EB> control tool for the patch if that is desired. I dislike the current
EB> implementation of the patch manager upload/download process. Besides, I can
EB> easily discuss it in my mailer without having to load up YAGUI window.
We currently have 18 bugs, 9 of which are open, and 24 patches, 12
of which are open. Do you remember what those bugs and patches? I, no.
But I know that those open bugs are outside current scope of our work,
and many hang there for more than month. Will you be eager to hunt for
such submissions when they would come into scope? Realistically, I
wouldn't. Moreover, time when I finally can go thru submissions is
when I'm away from my production box (and mail), where I can spend
time more productively. This all lead me to recognitaion of the fact
that submissions which are not processed during week are effectively
lost, unless they are made via facility which allows to track and
provide access to them properly. Yes, this requires a bit more effort,
but it leads to preserving of content, whereas more "easy" techniques
not so reliable in this respect.
With all that, feel free to run quick discussions within our team
wherever you want - after all, Earnie, you process most patches
and Danny submits most of them. But if you'll come to decision that some
patch cannot be accepted, entire discussion would better be attached
to that patch.
EB> Earnie Boyd
Paul Sokolovsky, IT Specialist