From: Eric Wong <e@80x24.org>
To: Askar Safin <safinaskar@gmail.com>
Cc: meta@public-inbox.org
Subject: Re: [BUG] Subject is wrong
Date: Tue, 9 Jan 2024 06:10:28 +0000 [thread overview]
Message-ID: <20240109061028.M784186@dcvr> (raw)
In-Reply-To: <CAPnZJGAe4uLkfu-S8peWmO_T-wmW1OV=vaLOe-yYZNKQg04SbQ@mail.gmail.com>
Askar Safin <safinaskar@gmail.com> wrote:
> Hi. I found bug in public-inbox.
> Consider this link:
> https://lore.kernel.org/linux-mm/202401080923.A8F568C2FA@keescook/
> In the bottom you will see this:
> *=*=*=*=*=*=*=*=
> Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
> 2023-12-27 0:31 [PATCH] exec: remove useless comment Askar Safin
> 2024-01-08 17:24 ` Kees Cook [this message]
> 2024-01-09 3:04 ` [PATCH RESEND] " Askar Safin
That's intentional, '"' (\x22) is used as the "ditto mark" meaning
that part of the subject is the same as above:
https://en.wikipedia.org/wiki/Ditto_mark
It cuts down on visual noise IMHO.
prev parent reply other threads:[~2024-01-09 6:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-09 3:47 [BUG] Subject is wrong Askar Safin
2024-01-09 6:10 ` Eric Wong [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
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240109061028.M784186@dcvr \
--to=e@80x24.org \
--cc=meta@public-inbox.org \
--cc=safinaskar@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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).