[EMAIL PROTECTED] (Karl Berry) writes:
> Haven't we implicitly been assuming/providing malloc-gnu since day 1?
> Do we really need to force all gnulib users ('cause pretty much everyone
> needs malloc, after all) to educate themselves about the issue and make
> a choice? Can we just keep malloc as malloc-gnu?
I don't have a strong preference, but I am lazy so my mild preference
is to leave it alone.
Perhaps renaming "malloc" to "malloc-gnu" should wait until we've done
a survey of other modules in the same boat? Surely malloc is not the
only module with this problem.
