> That's a work-flow problem. Either we can do a patch-based email
> workflow like Linux does, or we can attach patches to bugzilla bugs. The
> latter has less potential for things to get lost if fewer people are
> around, so everybody here so far seems to suggest doing that.
Indeed, we do need a work flow. "Things don't get lost" is the point
of view taken by those who make new entries, of course. ;-)
Originally, there was a complaint that bugzilla issues tend to lack
feedback. Obviously, the current situation is not very attractive to
those who might reply.
> Hence, the information on that particular patch can be found in the
> bugzilla "tracker item" (http://bugs.exim.org/show_bug.cgi?id=139) and I
> see little sense sending it to the mailing list in addition to the
> bugzilla mails that already cross this list.
Oh my god. 7 items marked out, a lenghty discussion without summary and
a diff as 8th item. Where is the description of the chosen approach? Do
you expect people apply the patch just to look what they have got? Indeed,
sending THAT to exim-dev would be useless.
Michael
