I wonder why pax-utils.eclass uses elog instead of just einfo. An
example message looks like this:

 * Fallback PaX marking -m
 *      out/Release/chrome

IMHO it's not very useful in the elog messages, but maybe there are
scenarios in which it is useful.

My idea is to just replace all elogs with einfos in pax-utils.eclass.
What do you think?

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to