Follow-up Comment #6, sr #111305 (group administration): On Tue, Aug 26, 2025 at 03:29:52PM -0400, Keith Marshall wrote: > > That said, my own [https://savannah.gnu.org/bugs/index.php?60927#comment13 > comment #13], on that same https://savannah.gnu.org/bugs/?60927 ticket > mentioned in [comment #0 my original submission], illustrates a further > issue, > which a ticket editing capability could mitigate: that particular comment > includes a less than obvious typo, (U+2009 where I intended U+200B). I'd > love > to be able to fix that, but without a ticket editing capability, I cannot do > so.
How do people fix such things on mailing lists? They post a follow-up.
> Perhaps less relevant on savannah, but FWIW, the most common reason for using
> this capability SourceForge, and on OSDN.net, was to correct the markup of
> code samples, posted by user who didn't bother to acquaint themselves with
> the
> appropriate markup conventions; I would encounter this in original ticket
> submissions, just as often as in follow up comments; the usual effect was
> that
> the code samples became unreadable, because elements of the code, which the
> users were trying to illustrate, would be interpreted as markup.
> Fortunately,
> correction was possible, because an editing capability was available to the
> original posters of malformed content, and to authorised project members.
Enabling changes would result in two kinds of potential confusions,
* The actual author of the post may differ from the original poster.
* The user can't rely on the accessibility of any fixed comment.
If we implement editing, I think we should work out some features
to mitigate them, e.g. limit editing to one time, with the original
post being easily available.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/support/?111305>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
