From: Richard Copley <rcopley@gmail.com>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Andreas Schwab <schwab@linux-m68k.org>,
Drew Adams <drew.adams@oracle.com>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: [offtopic] Gmail "conversations" splitting up from time to time
Date: Tue, 5 May 2020 22:34:42 +0100 [thread overview]
Message-ID: <CAPM58ohJx2i_XnsLuOsd5zCKrUr5EP_LUW_M1rm5xmBONXzg-Q@mail.gmail.com> (raw)
In-Reply-To: <CADwFkmk04qytQ6txAihcybi4vOJ0ZJGX6g_RUVEi5cAU2e4s5g@mail.gmail.com>
On Tue, 5 May 2020 at 22:15, Stefan Kangas <stefankangas@gmail.com> wrote:
>
> Andreas Schwab <schwab@linux-m68k.org> writes:
>
> >> I noticed that my Gmail threads started to be all split up.
> >
> > Threads are defined by In-Reply-To and References headers, not by
> > Subject.
>
> Unfortunately no one has explained this to the GMail developers.
It mostly seems to work fine. Bugs can creep in here and there, but I
don't think we can pin this one on Google Mail.
In the case of the reply from Drew I mentioned earlier, the copy
received by the GNU list server has the same mangled message-id. It
can be seen at <https://lists.gnu.org/archive/mbox/emacs-devel/2020-05>.
In an ideal world, Drew's organisation's IT department might like to
take it up with Microsoft.
prev parent reply other threads:[~2020-05-05 21:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 20:08 [offtopic] Gmail "conversations" splitting up from time to time Philippe Vaucher
2020-05-05 20:21 ` Yuri Khan
2020-05-05 20:34 ` Drew Adams
2020-05-06 9:24 ` Philippe Vaucher
2020-05-05 21:02 ` Andreas Schwab
2020-05-05 21:11 ` tomas
2020-05-05 21:11 ` Richard Copley
2020-05-05 21:13 ` Stefan Kangas
2020-05-05 21:34 ` Richard Copley [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPM58ohJx2i_XnsLuOsd5zCKrUr5EP_LUW_M1rm5xmBONXzg-Q@mail.gmail.com \
--to=rcopley@gmail.com \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=schwab@linux-m68k.org \
--cc=stefankangas@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.