From: Jeff King <peff@peff.net>
To: Aaron Schrab <aaron@schrab.com>
Cc: postmaster@vger.kernel.org, "Kerry,
Richard" <richard.kerry@atos.net>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Has there been a change in Git Mailing List settings? From list as sender to originator as sender?
Date: Fri, 18 Sep 2020 19:28:05 -0400 [thread overview]
Message-ID: <20200918232805.GA1197580@coredump.intra.peff.net> (raw)
In-Reply-To: <20200918225326.GA1367@pug.qqx.org>
[+cc postmaster@vger; it looks like messages to the git-list stopped
including a Sender header as of a few days ago]
On Fri, Sep 18, 2020 at 06:53:26PM -0400, Aaron Schrab wrote:
> > Not to my knowledge. The smtp-level envelope from on all of the messages
> > I've received is git-owner@vger.kernel.org. Is there some other
> > mechanism you might be filtering on?
>
> Comparing <20200911143321.GA2374950@coredump.intra.peff.net> with the
> message I'm replying to so that I'd have messages which I would expect to be
> similar before the list handling I see that that older message included the
> header
>
> Sender: git-owner@vger.kernel.org
>
> But the newer message does not have a Sender: header.
Ah, thanks. I even looked for a Sender header, but I stupidly looked at
too-recent messages, which of course didn't have one. :)
According to my local archive, we stopped getting Sender headers around
1600296026 (that's the timestamp when I received it), which was
Date: Wed, 16 Sep 2020 17:11:50 -0400
Subject: Re: [PATCH 3/5] t3200: avoid variations of the `master` branch name
https://lore.kernel.org/git/20200916211150.GA617237@coredump.intra.peff.net/
The message I received right before that was:
Date: Wed, 16 Sep 2020 14:25:42 -0700
Subject: Re: [PATCH 2/5] t/test-terminal: avoid non-inclusive language
https://lore.kernel.org/git/xmqqo8m5v2g9.fsf@gitster.c.googlers.com/
which does have a Sender header (note those are out of order if you
believe the client-side Date headers).
> I don't know if that was a deliberate change.
I don't know, but we don't really admin the list ourselves. kernel.org
folks do, so they might have input.
-Peff
next prev parent reply other threads:[~2020-09-18 23:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 10:11 Has there been a change in Git Mailing List settings? From list as sender to originator as sender? Kerry, Richard
2020-09-17 13:01 ` Jeff King
2020-09-18 22:53 ` Aaron Schrab
2020-09-18 23:28 ` Jeff King [this message]
2020-09-19 1:44 ` Konstantin Ryabitsev
2020-09-21 9:22 ` Kerry, Richard
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: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200918232805.GA1197580@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=aaron@schrab.com \
--cc=git@vger.kernel.org \
--cc=postmaster@vger.kernel.org \
--cc=richard.kerry@atos.net \
/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://80x24.org/mirrors/git.git
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).