Follow-up Comment #7, bug #67939 (group groff):

[comment #6 comment #6:]
> Solutions to such issues exist already.  The people at the
> other end are responsible for their application.

If you've been following the groff mailing list lately, you'll have noticed
that the groff project is taking great care to make its code work on as wide a
variety of platforms as possible.  In general, if you want your contributions
accepted into a collaborative open-source project, you should adhere to that
project's goals and style.  So I'd recommend coding with maximal portability
here.

> I see no valid reason to make two or more tickets for such changes

I agree that multiple tickets are unnecessary.  But you can include multiple
patches in the same ticket, and these changes strike me as warranting separate
commits.  However, that ruling is ultimately above my pay grade, so I defer to
those with commit privileges.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?67939>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/

Attachment: signature.asc
Description: PGP signature

Reply via email to