> On 6 Oct 2025, at 03:19, Ben Boeckel <[email protected]> wrote: > > On Fri, Oct 03, 2025 at 07:37:29 +0100, Iain Sandoe wrote: >> Looks like a good cleanup - one comment >> >>> On 3 Oct 2025, at 03:03, Ben Boeckel <[email protected]> wrote: >>> These patches update the email address for gcc-patches@ and replaces >>> gcc-bugs@ references with a link to the "how to report a bug" page. >> >> It reads a bit strangely to me to say “Report bugs to …” (and variations) and >> then to point to the instructions. >> >> Maybe either point to bugzilla or alter the wording to say “How to report a >> bug.." > > I can fix some of them. But the ones in `configure` scripts are editing > generated code. I feel like the bug reporting instructions are far more > useful than dumping someone at Bugzilla. Either a crap report is filed > or someone who wouldn't have made a good report anyways won't read the > instructions to make a good report. But if you think it is better to > have (running-configure-related) issues reported that don't follow the > instructions, then I can update that. Unfortunately, I don't think > editing the wording around those generated bits will survive long. Yeah, indeed, that seems baked into auto* tools .. so, yes, the instructions are probably better than just pointing at bugzilla. No further comments from me - presumably, this needs approval from a build machinery maintainer. thanks Iain > > Thanks, > > --Ben
