Re: Viewing patches in bugzilla just got easier and nicer

[Gabriel Dos Reis <gdr at integrable-solutions dot net>]

Daniel Berlin <dberlin@dberlin.org> writes:

| On Sat, 8 Jan 2005, Gabriel Dos Reis wrote:
| 
| > Daniel Berlin <dberlin@dberlin.org> writes:
| >
| > | On Sat, 8 Jan 2005, Gabriel Dos Reis wrote:
| > |
| > | > Daniel Berlin <dberlin@dberlin.org> writes:
| > | >
| > | > | > Thanks.
| > | > | >
| > | > | > | Did you also want it to pass through the message-id?
| > | > | >
| > | > | > Do you mean the message-id generated by say my MUA?  Yes.
| > | > |
| > | > | This should happen now too.
| > | >
| > | > again, thanks!
| > |
| > | I don't of course, guarantee that this will actually do anything useful.
| > | I still don't believe it's going to thread like you want.
| > |
| > | See the string of messages on 19332, for examples.
| >
| > I don't think bugzilla updates the References:.  In that thread, they
| > are the same, except for the first message.
| 
| What exactly do you want the references to be?

For example it you look at your messsage (I'm replying to), you have

   References: <Pine.LNX.4.60.0501071659370.24186@dberlin.org>
            <m3fz1c7tu4.fsf@uniton.integrable-solutions.net> 
            <Pine.LNX.4.60.0501071734440.24186@dberlin.org>
            <m3acrk7rs5.fsf@uniton.integrable-solutions.net> 
            <Pine.LNX.4.60.0501071822150.24186@dberlin.org>
            <m3sm5c69h3.fsf@uniton.integrable-solutions.net> 
            <Pine.LNX.4.60.0501081201020.27085@dberlin.org>
            <m3llb325xh.fsf@uniton.integrable-solutions.net> 
            <Pine.LNX.4.60.0501081335490.30941@dberlin.org>
            <m3fz1b21hw.fsf@uniton.integrable-solutions.net> 
            <Pine.LNX.4.60.0501081415560.31501@dberlin.org>
            <m3acrj1zvl.fsf@uniton.integrable-solutions.net> 
            <Pine.LNX.4.60.0501081434390.31501@dberlin.org>
            <m3y8f3zi5w.fsf@uniton.integrable-solutions.net>

If you at this message (I'm writing), you'll see

   References: <Pine.LNX.4.60.0501071659370.24186@dberlin.org>
           <m3fz1c7tu4.fsf@uniton.integrable-solutions.net>
           <Pine.LNX.4.60.0501071734440.24186@dberlin.org>
           <m3acrk7rs5.fsf@uniton.integrable-solutions.net>
           <Pine.LNX.4.60.0501071822150.24186@dberlin.org>
           <m3sm5c69h3.fsf@uniton.integrable-solutions.net>
           <Pine.LNX.4.60.0501081201020.27085@dberlin.org>
           <m3llb325xh.fsf@uniton.integrable-solutions.net>
           <Pine.LNX.4.60.0501081335490.30941@dberlin.org>
           <m3fz1b21hw.fsf@uniton.integrable-solutions.net>
           <Pine.LNX.4.60.0501081415560.31501@dberlin.org>
           <m3acrj1zvl.fsf@uniton.integrable-solutions.net>
           <Pine.LNX.4.60.0501081434390.31501@dberlin.org>
           <m3y8f3zi5w.fsf@uniton.integrable-solutions.net>
           <Pine.LNX.4.60.0501081713200.31501@dberlin.org>

Notice, the last line is the message-id of the message I'm replying to.

Assume bugzilla receives message M.  That M usually already contains a
References: (when it is a reply).  Let bugzilla preserve that in its database. 
Furthermore, associate the comment number (used internally by bugzilla
to number comments in PRs) with the message-id of M.

When User replies to comment N, the new message containing that
comment should include in its header

  (1) Message-ID:  
       a unique reference (not that of the seed) identifying the reply.

  (2) References: 
         The References: in comment N, plus the Message-ID of
         comment N.

-- Gaby