Re: 'notmuch search thread:<>' lists multiple threads

David Bremner wrote: "Naveen N. Rao" writes: David Bremner wrote: David Bremner writes: At least some of this mail data is public, but I'm not sure if the bad threading is reproducible or not; I want to run a complete census overnight before I reindex. Even if the bug is

Re: 'notmuch search thread:<>' lists multiple threads

"Naveen N. Rao" writes: > David Bremner wrote: >> David Bremner writes: >> >>> At least some of this mail data is public, but I'm not sure if the bad >>> threading is reproducible or not; I want to run a complete census >>> overnight before I reindex. >>> >>> Even if the bug is

Re: 'notmuch search thread:<>' lists multiple threads

Naveen N. Rao wrote: David Bremner wrote: David Bremner writes: "Naveen N. Rao" writes: Were you able to look into this again? Using a list of in-reply-to values sounds like a good option, though I clearly have no idea about other consequences from that. If you have a patch, I can help

Re: 'notmuch search thread:<>' lists multiple threads

Naveen N. Rao wrote: Naveen N. Rao wrote: David Bremner wrote: David Bremner writes: "Naveen N. Rao" writes: Were you able to look into this again? Using a list of in-reply-to values sounds like a good option, though I clearly have no idea about other consequences from that. If you

Re: 'notmuch search thread:<>' lists multiple threads

David Bremner wrote: David Bremner writes: "Naveen N. Rao" writes: Were you able to look into this again? Using a list of in-reply-to values sounds like a good option, though I clearly have no idea about other consequences from that. If you have a patch, I can help test that. Sorry

Re: 'notmuch search thread:<>' lists multiple threads

David Bremner writes: > "Naveen N. Rao" writes: > >> >> Were you able to look into this again? >> Using a list of in-reply-to values sounds like a good option, though I >> clearly have no idea about other consequences from that. If you have a >> patch, I can help test that. >> > > Sorry I

Re: 'notmuch search thread:<>' lists multiple threads

"Naveen N. Rao" writes: > > Were you able to look into this again? > Using a list of in-reply-to values sounds like a good option, though I > clearly have no idea about other consequences from that. If you have a > patch, I can help test that. > Sorry I haven't made any progress on this.

Re: 'notmuch search thread:<>' lists multiple threads

Hi David, David Bremner wrote: "Naveen N. Rao" writes: In my case, I seem to be having the In-Reply-To headers. I end up with two files per message: one from my inbox and one from the gmane archive that I pull in. All the messages from the gmane archive seem to have a re-written

Re: 'notmuch search thread:<>' lists multiple threads

"Naveen N. Rao" writes: > In my case, I seem to be having the In-Reply-To headers. I end up with > two files per message: one from my inbox and one from the gmane archive > that I pull in. All the messages from the gmane archive seem to have a > re-written

Re: 'notmuch search thread:<>' lists multiple threads

David Bremner wrote: David Bremner writes: At least some of this mail data is public, but I'm not sure if the bad threading is reproducible or not; I want to run a complete census overnight before I reindex. Even if the bug is non-deterministic, it probably lives in

Re: 'notmuch search thread:<>' lists multiple threads

David Bremner writes: > At least some of this mail data is public, but I'm not sure if the bad > threading is reproducible or not; I want to run a complete census > overnight before I reindex. > > Even if the bug is non-deterministic, it probably lives in lib/add-message.cc I

Re: 'notmuch search thread:<>' lists multiple threads

"Naveen N. Rao" writes: > Greetings-- > If I search for threads matching a specific thread-id, I am seeing > multiple results: > > $ notmuch search --output=threads thread:000c4d20 > thread:000c4d1e > thread:000c4d20 This looks like a

Re: 'notmuch search thread:<>' lists multiple threads

Naveen N. Rao wrote: Greetings-- If I search for threads matching a specific thread-id, I am seeing multiple results: $ notmuch search --output=threads thread:000c4d20 thread:000c4d1e thread:000c4d20 Expanding on this: [04/06 15:37:59 ~]$ notmuch search