In ruby 1.8 branch I see REXML completely reorganized so there's
basically no way to submit a patch until you know where 1.8 is headed.
Could someone shed some light on it?
--
MK
Yes. A patch fix supplied by a contributor was applied that introduced this
regression. There was no unit test that would have caught this, so it ended
up being propagated back to the Ruby trunk.
This has been fixed in the REXML repository, and a unit test has been
introduced to catch any future regressions (of this feature). It hasn't yet
made it into the Ruby repository, but will soon.
Of course, special dispensation will need to be gained for code freezes.
--
### SER
### Deutsch|Esperanto|Francaise|Linux|XML|Java|Ruby|Haskell|Aikido|Iaido
### http://www.ser1.net, http://www.ser1.net/Security/ser_public.gpg
### Jabber: seaner...@gmail.com (OTR enabled)