This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Future of gccbug
"Zack Weinberg" <zack@codesourcery.com> writes:
| Gabriel Dos Reis <gdr@integrable-solutions.net> writes:
|
| > Daniel Berlin <dberlin@dberlin.org> writes:
| >
| > | We don't actually track message ids of each sent out mail right now.
| > | Even if we did, we don't know what comments are replies to other
| > | comments, so it's not possible to do anything other than put them
| > | under the first one.
| >
| > Precisely because you don't, it is a pain to see which messages
| > follow up to which messages. One needs to connect to the bugzilla
| > database to see a flat thread with "comment #foo".
| > Sending bugzilla mails thus seem to be useless.
|
| I think, what you are asking for is not practical without adding full
| support for threaded replies to bugzilla itself. This would be nice
| (and has been implemented successfully in other "web discussion" media
| - see e.g. Slashdot nested mode) but would be a lot of work which I do
| not think it is fair to ask Daniel to do.
|
| An alternate idea, which also gets round the gcc-bugzilla/gcc-bugs
| headache: Have gcc-bugs be the primary, with messages sent directly
| there -- threading then Just Works.
If it works, then I buy it.
-- Gaby