Follow-up Comment #31, bug #66583 (group groff): To clear up a point about CCing and bug traffic:
At 2024-12-29T20:06:30+0100, Alejandro Colomar wrote: > On Sun, Dec 29, 2024 at 01:49:29PM -0500, anonymous wrote: >>>> The problem Alex was experiencing, though, occured with a version >>>> which groff accepted. >>> >>> Okay, well, he should be getting CCed on this so maybe he can put >>> us in the picture. >> >> I agree, but you're saying that to the wrong person. I did in fact mean to use the passive voice. Savannah has a CC system (scroll to the bottom of a bug report on its web UI and note the "Carbon-Copy List" blinder. It also accepts emailed replies to ticket comments, under certain circumstances: see the quoted material below. > I do have an account. :) > > I don't know why my mail didn't reach the savannah. If you didn't comment via the web UI, or didn't follow the email procedure below, that'd be why. > Maybe it didn't have enough metadata to go through the system that > reads mail and transforms it into posts. Not enough zebras. :| It's more synchronous than that, and has fairly stringent criteria, I'm sure to erect a high barrier to spam. I don't think anything scrapes mailing list archives for messages to append to Savannah tickets. When Savannah emails me about a groff ticket, the message has a footer like the following. To reply to this notification, you have two options: * In the Web UI at <https://savannah.gnu.org/bugs/?66583>. * By email, ONLY IF you sign your email with a GPG key registered in your Savannah account AND you include the following line in the reply: _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?66583> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
signature.asc
Description: PGP signature
