From: Bart Schaefer <schaefer@brasslantern.com>
To: Mikael Magnusson <mikachu@gmail.com>
Cc: Marlon Richert <marlon.richert@gmail.com>,
Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Patch 1/3: Fix prefix insertion logic
Date: Sat, 6 May 2023 10:23:10 -0700 [thread overview]
Message-ID: <CAH+w=7ZvnxEHYi1=VgaP6VApWWSCvNdbR7FQ6hqigeb8fEtzew@mail.gmail.com> (raw)
In-Reply-To: <CAHYJk3T_oo5fW8tus4BtoORwk_gRQGq21jgFOa+WVNWW8RQZcA@mail.gmail.com>
On Fri, May 5, 2023 at 8:04 AM Mikael Magnusson <mikachu@gmail.com> wrote:
>
> On 5/5/23, Marlon Richert <marlon.richert@gmail.com> wrote:
> > However even though I used the same message ID, the new mails did not
> > end up in the same thread.
>
> If you're looking in the gmail web interface, the reason is that gmail
> doesn't support threads (it ignores all thread information and only
> groups mails with the same subject line).
The one exception to this is that gmail will treat messages with
identical message-id as duplicates and only show one of them. That's
why e.g. if you send a message to the list using gmail it'll appear
only in your Sent label and seem not to have come back to you via the
list.
I'm not sure what would happen if it were presented with identical
message-id and radically different message bodies, but in my
experience small differences in the body do not affect this.
Looks like something (git send-email maybe?) appended -1 / -2 / -3 to
the message-id in each of these patches, which are otherwise the same.
next prev parent reply other threads:[~2023-05-06 17:23 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-29 18:07 Marlon Richert
2023-04-29 18:08 ` Patch 2/3: Make dynamic dir completion easier to implement Marlon Richert
2023-04-29 18:09 ` Patch 3/3: Fix subscript completion bugs inside ~[...] Marlon Richert
2023-04-29 18:58 ` Patch 1/3: Fix prefix insertion logic Felipe Contreras
2023-04-29 19:02 ` Marlon Richert
2023-04-29 19:17 ` Bart Schaefer
2023-05-01 21:08 ` Aaron Schrab
2023-05-01 22:03 ` Bart Schaefer
2023-05-05 11:41 ` [PATCH 1/3] Fix _prefix " Marlon Richert
2023-06-07 6:03 ` Marlon Richert
2023-06-08 12:41 ` Jun. T
2023-06-15 14:11 ` Marlon Richert
2023-05-05 11:41 ` [PATCH 2/3] Make dynamic dir completion easier to implement Marlon Richert
2023-05-06 17:28 ` Bart Schaefer
2023-05-13 17:30 ` Bart Schaefer
2023-05-15 9:04 ` Oliver Kiddle
2023-05-05 11:41 ` [PATCH 3/3] Fix subscript completion bugs inside ~[...] Marlon Richert
2023-05-01 22:37 ` Patch 1/3: Fix prefix insertion logic Felipe Contreras
2023-05-01 22:52 ` Bart Schaefer
2023-05-02 4:49 ` Felipe Contreras
2023-05-02 19:16 ` Bart Schaefer
2023-05-02 20:14 ` Felipe Contreras
2023-05-05 11:51 ` Marlon Richert
2023-05-05 12:38 ` Felipe Contreras
2023-05-05 15:04 ` Mikael Magnusson
2023-05-06 17:23 ` Bart Schaefer [this message]
2023-05-01 23:36 ` Vin Shelton
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='CAH+w=7ZvnxEHYi1=VgaP6VApWWSCvNdbR7FQ6hqigeb8fEtzew@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=marlon.richert@gmail.com \
--cc=mikachu@gmail.com \
--cc=zsh-workers@zsh.org \
/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 public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).