All,

this is a followup to the original message that started this thread.

A case has been made for librc, but not libeinfo. There could be reasons
to allow the librc functionality to stay around, but I'm not convinced
wrt libeinfo, especially since there are no consumers.

Does anyone see a reason we should keep the einfo/eerror/etc c functions
in a public API?

William

Attachment: signature.asc
Description: Digital signature

Reply via email to