On Fri, Dec 19, 2025, at 2:12 AM, Gerald Pfeifer wrote:
> On Thu, 18 Dec 2025, Pietro Monteiro wrote:
>> They should be sent to both the Algol 68 list and gcc-patches.
>
> Makes sense.
>
>> Suggested-by: Mohammad-Reza Nabipoor <[email protected]>
>> Signed-off-by: Pietro Monteiro <[email protected]>
>
> For changes like these, that update existing Algol 68 material or add
> relevant updates to other pleses, feel free to push and just share on
> gcc-patches. This is just an offer, not a request - I am happy to review
> and approve anything wwwdocs.
>
> For wwwdocs changes, would you mind adding [wwwdocs] to the mail subject
> per our conventions? This makes them stand out for people interested (and
> indeed I do have filters).
Yes. Sorry I forgot to do that. I configured git format-patch to do that
automatically for wwwdocs for now on. BTW, I added this to .git/config:
[format]
subjectPrefix = PATCH] [wwwdocs
>> end of GCC, and the corresponding runtime library. Patches to ga68
>> - and libga68 should go to this list.</li>
>> + and libga68 should be sent to both this list and <b>gcc-patches</b>.</li>
>
> Looks good, thank you.
Thanks. I just committed and pushed this patch.
> I have, over the years, read and been told to prefer active tense in
> technical documentation. If you agree, you could rephrase this as "Send
> patches for ga68 and libga68 to both this list and <b>gcc-patches</b>" or
> similar.
I was keeping it consistent with the directions for other lists, ex.:
"Patches to libstdc++-v3 should be sent to both this list and
gcc-patches."
> (This is not a requirement; the patch is fine either way.)
>
> Gerald
pietro
