On Tue, May 10, 2016 at 01:10:00PM -0700, Yoshiki Vazquez-Baeza wrote: > On (May-10-16|13:02), Will Yardley wrote: > > I think "conversations" in Gmail are essentially the same thing as > > threads, no? > > As you mention, this depends on the settings you have. However if I > understand correctly, the structure of a thread is determined by the > in-reply-to header attribute. GitHub does not include this attrribute in > the emails they send you, so all your emails are piled in a single > thread but with no thread structure on their own, as far as I know, > there's no way to fix this. Gmail on the other hand will just order > these as you expect: > > Message 1 > Message 2 > Message 3 > > Mutt will do this: > > Message 3 > Message 2 > Message 1
Well the 123 vs. 321 thing might be more due to what $sort_aux is set to (i.e., whether sorting by received time / date header, or reverse). I'm not sure which Github emails you're seeing (and obviously Github is only one example), but the examples I find from them (for both issue tracking and pull requests) *are* threaded properly in Mutt (that is, related messages are tied together; unrelated messages are not). For example, from a bug report / issue tracking request: Message-ID: <someuser/somerepo/issues/731/211759...@github.com> In-Reply-To: <someuser/somerepo/issues/7...@github.com> or from a pull request: Message-ID: <foo/repo/pull/86/issue_event/656085...@github.com> In-Reply-To: <foo/repo/pull/8...@github.com> References: <foo/repo/pull/8...@github.com> The latter shows up like this for me in Mutt when threads are expanded: 4191 May 10 someone ( 51K) [foo/repo] Merging ..... > .... 4192 May 10 someone ( 50K) `-> 4193 May 10 someone ( 49K) `=> 4194 May 10 someone ( 53K) [foo/repo2] Blah blah blah 4195 May 10 someone ( 53K) |=> 4196 May 10 someone ( 50K) `-> and like this when collapsed: 4191 May 10 someone ( 51K) 3 [foo/repo] Merging ..... > .... 4194 May 10 someone ( 53K) 3 [foo/repo2] Blah blah blah w
