The mailing list is managed through SourceForge, so it will depend if SourceForge provides such an ability to tweak the list. I'll check into this.
> The digest processing apparently waits until it has accumulated > > ~10 messages before it sends out a digest. I subscribe to 3 of the > > FreeDOS mailing lists (User, Devel, Kernel) and AFAICT all three of > > them do this. > > > > The problem is, on lists with infrequent posts, it takes a long > > time to accumulate ~10 messages. So, by the time that a digest is > > finally sent out, the older messages in that digest may be weeks or > > months old. In many cases, the info in those messages is out of > > date by the time a digest subscriber (like me) sees it. > > > > E.g. I received a digest from the FreeDOS-kernel mailing list on > > September 17th. The first message in that digest was dated July > > 28th. If the poster of that msg had wanted a response from other > > list subscribers, he would have been denied any chance of a response > > from digest subscribers because of the way digest processing is > > done. > > > > Of the three mailing lists that I mentioned, the kernel list > > suffers the most from this effect. That's because the kernel list > > usually receives the fewest posts. But even digests from the devel > > and user lists are sometimes delayed this way. > > > > May I suggest that each list's digest processor be changed so > > that it sends out at least one digest on any day when someone posts > > to that list? > > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Freedos-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-devel
