Hi Morgan, Morgan Smith <[email protected]> writes:
> Sometimes bug reports get really big and it takes a long time to read > the whole thing. Yes, I understand the need. IMO introducing a new concept of "summary" would be too complex. Also, it seems no debbugs users really use this, probably for a reason. When playing with the idea, I came up with many questions: for ordinary reports, should we infer what is a summary? perhaps the first paragraph? The commit message for patches? Shall we fall back on the subject when the email only contains a (supposedly) self-explanatory inline diff? Instead, I implemented a new directive "Supersedes", the little sister of the already existing "Superseded-by". In a thread about a bug that needs a summary, you can reply by changing the subject (if needed), by writing the bug summary in your email and then writing, in any place of your email: "Supersedes: https://list.orgmode.org/orgmode/messageid@domain/"; (Or a <message-id>, same syntax than "Superseded-by".) This way: - The old bug report is closed; - The new bug report replaces it (with a proper summary); - The two reports are still related and visible as such in the UI. Let me know how it works for you in practice, thanks for raising this issue. -- Bastien
