Slow CVS-log email updates to fvwm-workers@

2010-06-13 Thread Thomas Adam
Hi all, Is it just me, or are the usual CVS commit log emails which get sent out every time someone does a "cvs commit" taking hours to come through? It seems that way to me. Jason, anything funky going on at your end, out of interest? I don't recall them being this slow -- usually the emails w

CVS tadam: Minor typo corrections to developer-cvs/todo-2.6 docs.

2010-06-13 Thread cvs
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: tadam 10/06/13 05:38:44 Modified files: docs : ChangeLog DEVELOPER-CVS todo-2.6 Log message: Minor typo corrections to developer-cvs/todo-2.6 docs.

Re: FVWM: next stable release? (dont shoot!)

2010-06-13 Thread Thomas Adam
On Sun, Jun 13, 2010 at 03:16:39PM +0100, Michael Treibton wrote: > hi! > > On 13 June 2010 10:12, Thomas Adam wrote: > > If you or *anyone* else wanted to actually help, by all means look at > > writing more purify tests -- that alone would likely throw up some > > interesting bugs if they were

CVS tadam: Clarify that typos in purify/purify.fvwm2rc are *deliberate*

2010-06-13 Thread cvs
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: tadam 10/06/13 15:49:43 Modified files: tests : ChangeLog tests/purify : README Log message: Clarify that typos in purify/purify.fvwm2rc are *deliberate* They're there to test FVWM's (in)tolerance

CVS tadam: Add point "F5" -- another release-critical bug blocking 2.6.0

2010-06-13 Thread cvs
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: tadam 10/06/13 16:13:42 Modified files: docs : ChangeLog todo-2.6 Log message: Add point "F5" -- another release-critical bug blocking 2.6.0 We'll eventually reduce this, I promise. :)