Incorrect/lacking References in mail headers?
Conor Dooley <[email protected]> Tue, 19 May 2026 10:54:44 +0100
| Newsgroups | dev.linux.lists.sashiko |
|---|---|
| Message-ID | <20260519-google-salary-aab923033a86@spud> |
--sAFs8W7Ws+5pjmo8 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Yo, I think the mails coming from sashiko-bot don't have the correct References headers set. When I have deleted a thread that I don't care about before the sashiko-bot mails come through I end up with my inbox looking like: | 99 N May 19 sashiko-bot@ker (6.1K) Re: [PATCH v6 14/16] wifi: ath12k: = Switch to generic PAS TZ APIs | 100 ND May 19 sashiko-bot@ker (7.0K) Re: [PATCH v6 12/16] media: qcom: P= ass proper PAS ID to set_remote_state API | 101 N May 19 sashiko-bot@ker (7.2K) Re: [PATCH v6 11/16] media: qcom: S= witch to generic PAS TZ APIs | 102 N May 19 sashiko-bot@ker (6.8K) Re: [PATCH v6 10/16] drm/msm: Switc= h to generic PAS TZ APIs | 103 ND May 19 sashiko-bot@ker (8.8K) Re: [PATCH v6 05/16] remoteproc: qc= om_q6v5_pas: Switch over to generic PAS TZ APIs | 104 N May 19 sashiko-bot@ker (8.9K) Re: [PATCH v6 04/16] firmware: qcom= : Add a PAS TEE service | 105 ND May 19 sashiko-bot@ker (8.3K) Re: [PATCH v6 07/16] soc: qcom: mdt= loader: Switch to generic PAS TZ APIs | 106 N May 19 sashiko-bot@ker (7.0K) Re: [PATCH v6 06/16] remoteproc: qc= om_q6v5_mss: Switch to generic PAS TZ APIs | 107 ND May 19 sashiko-bot@ker (5.8K) Re: [PATCH v6 08/16] remoteproc: qc= om_wcnss: Switch to generic PAS TZ APIs | 108 N May 19 sashiko-bot@ker (7.3K) Re: [PATCH v6 02/16] firmware: qcom= : Add a generic PAS service | 109 ND May 19 sashiko-bot@ker (6.2K) Re: [PATCH v6 03/16] firmware: qcom= _scm: Migrate to generic PAS service | 110 N May 19 sashiko-bot@ker (6.7K) Re: [PATCH v6 01/16] arm64: dts: qc= om: kodiak: Add EL2 overlay In comparison, a more typical thread where I have deleted the original mails looks like: | 165 N May 19 Janani Sunil (8.3K) =E2=94=8C=E2=94=80>Re: [PATCH v2 = 2/3] iio: dac: Add AD5529R DAC driver support | 166 N May 19 Janani Sunil ( 12K) =E2=94=8C=E2=94=80=E2=94=B4=E2=94= =80>Re: [PATCH v2 2/3] iio: dac: Add AD5529R DAC driver support | 167 N May 19 Janani Sunil (9.3K) =E2=94=82 =E2=94=8C=E2=94=80>Re: [P= ATCH v2 1/3] dt-bindings: iio: dac: Add AD5529R | 168 N May 19 Janani Sunil (9.5K) =E2=94=82 =E2=94=9C=E2=94=80>Re: [P= ATCH v2 1/3] dt-bindings: iio: dac: Add AD5529R | 169 N May 19 Janani Sunil ( 10K) =E2=94=9C=E2=94=80=E2=94=B4=E2=94= =80>Re: [PATCH v2 1/3] dt-bindings: iio: dac: Add AD5529R | 170 N May 19 Janani Sunil (8.1K) =E2=94=B4=E2=94=80>Re: [PATCH v2 3/= 3] Documentation: iio: Add AD5529R Documentation The difference appears to be that Janani has a references header that cites the cover letter: In-Reply-To: <[email protected]> References: <[email protected]> <[email protected]> <20260508134843.7646c4f5@jic23-huawei> <[email protected]> Whereas your bot doesn't do this: In-Reply-To: <[email protected]> References: <[email protected]> Not only does it interfere with threading in my mailbox, it adds a load of extra steps to my process where one ctrl+d should suffice, given that I appear to get 100s of mails from the bot every day. Could you please try to resolve this? Thanks, Conor. --sAFs8W7Ws+5pjmo8 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEABYKAB0WIQRh246EGq/8RLhDjO14tDGHoIJi0gUCagwzZAAKCRB4tDGHoIJi 0gLaAQCCslK6utIRSMlyy1t/ydFmGlzTU0AGCIc8i5sZ7Cr4uQEAowJkQ/wzWUKs i0PefmG29uf00buAbYu6Gqz2NtiIrws= =B4xv -----END PGP SIGNATURE----- --sAFs8W7Ws+5pjmo8--