This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Future of gccbug


Phil Edwards <phil@jaj.com> writes:

| On Fri, Nov 07, 2003 at 09:11:59PM +0100, Gabriel Dos Reis wrote:
| > gnat-dev@buzco.nyct.net writes:
| > 
| > | I find the mail and WWW interfaces +both+ useful, but it would be nicer
| > | if bugzilla mail +visibly+ came from bugzilla.
| > 
| > I would add one more whish.  Threads managed by bugzilla is painful to
| > follow: The reason is that it does not keep proper references.  The end
| > result is a "flat" thread where every reply gets paranted by the first
| > message, instead of the usual thread tree.
| 
| Yes, it goes into "Kenner mode" because (the last time I investigated this,

And Dan keeps saying the contrary. :-(

[...]

| One little-known fact that has occasionally proved useful to me is that
| the mailing list software itself can serve up indices and retrieve old
| messages.  Before the web archives had a "view in raw mode" link, for
| example, and saving a patch from gcc-patches would change '>' into '&gt;',
| I would get the useful form of patches by sending a retrieval message to
| the list software, and getting a text version that way.  You could do the
| same thing with gcc-bugs, although it would be somewhat inconvenient.

I think that works only if one has the thread number.  What was
possible with GNATS is querying with the PR number.

-- Gaby


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]