public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Jan Beulich via Overseers <overseers@sourceware.org>
Cc: Jan Beulich <jbeulich@suse.com>
Subject: Re: unexpected list configuration change?
Date: Wed, 06 Sep 2023 11:41:32 +0200	[thread overview]
Message-ID: <6139a36551fbec18edf62bf87e462dfda5c9b2ba.camel@klomp.org> (raw)
In-Reply-To: <bf521282-c48e-16cd-1092-a8b26e903a96@suse.com>

Hi Jan,

On Wed, 2023-09-06 at 10:34 +0200, Jan Beulich via Overseers wrote:
> all of the sudden, when sending a 3-patch series just a few minutes ago,
> I've observed all Cc: disappearing from mails sent to/through the list.
> Quite some time ago I recall such happening for certain individuals, but
> aiui at that time it was a per-user choice. Of course with just two
> samples I can't exclude old behavior having been restored (and both of
> the people Cc-ed having that (mis-)feature turned on), but even then I
> would wonder why that was done. Stripping Cc-s makes replying more
> difficult, when on the reply you want to have the same set of Cc-s as
> was on the original mail.

There was an upgrade of mailman and a tweak to CC dropping:
https://sourceware.org/bugzilla/show_bug.cgi?id=29713#c42
That should have had the opposite behaviour, keep the CCs.

But the binutils list apparently sets it to Yes explicitly (or maybe
that was caused by the mailman upgrade):
https://sourceware.org/mailman/admin/binutils/?VARHELP=general/drop_cc
"Should duplicate avoidance drop addresses from Cc: headers" YES

I have explicitly set it to NO now.
Hopefully that fixes things.

Thanks for the report and please let us know if the above didn't fix
the issue.

Cheers,

Mark

      reply	other threads:[~2023-09-06  9:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-06  8:34 Jan Beulich
2023-09-06  9:41 ` Mark Wielaard [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=6139a36551fbec18edf62bf87e462dfda5c9b2ba.camel@klomp.org \
    --to=mark@klomp.org \
    --cc=jbeulich@suse.com \
    --cc=overseers@sourceware.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.
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).