> I agree. That is the reason that I only commited it to alpha22-rc > and not to MAIN. So that our release becomes more stable, and the > bug will still be visible in the development branch.
It does not become more stable. The problem is still there and another assert will be triggered later in code execution producing several differents bugs where there is only one in fact. > By the way: > when we upload the binaries to savannahs release website, it would > be a good time to exchange the buggy binaries with new ones that > work on more linux distribution, on more processors and have the > dirty fix for the this bug. I have tagged a proper candidate > with the tag name "alpha22" in the alpha22-rc branch. Yes Steph -- http://nct.ysagoon.com _______________________________________________ glob2-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/glob2-devel
