i just started working on a 2.1.5 system and discovered that this bug was still there. from looking in cvs, it appears to be fixed there (although it seems to reference an unrelated bugid).
updating this bug to reflect the cvs update would be nice.
i just started working on a 2.1.5 system and discovered that
this bug was still there. from looking in cvs, it appears
to be fixed there (although it seems to reference an
unrelated bugid).
updating this bug to reflect the cvs update would be nice.