workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: workflows@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH v1 2/2] Documentation: process: Recommend to put Cc: tags after cutter '---' line
Date: Tue, 23 Apr 2024 19:45:35 +0300	[thread overview]
Message-ID: <Ziflr9ag4Nl2lTic@smile.fi.intel.com> (raw)
In-Reply-To: <87ttjsqbld.fsf@intel.com>

On Tue, Apr 23, 2024 at 07:37:34PM +0300, Jani Nikula wrote:
> On Tue, 23 Apr 2024, Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:
> > On Tue, Apr 23, 2024 at 05:30:49PM +0300, Jani Nikula wrote:
> >> The Cc's on the mailing list archive are harder to dig up, and do not
> >> accurately reflect the same information.
> >
> > How comes? These Cc: are 1:1 mapped to the Cc: email headers.
> 
> Patch Cc's get mapped to email Cc's depending on personal git sendemail
> configuration.
> 
> People can add more Cc's in the emails when sending.

So, which exactly a proof why email headers are better for that, as they
reflect _reality_.

> Mailing list Cc's actually present in the archives depend on mailing
> list manager configuration, and, in some cases, even the personal list
> preferences of individual subscribers.

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2024-04-23 16:45 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-23 13:19 [PATCH v1 0/2] Documentation: process: Clarify use of Cc: Andy Shevchenko
2024-04-23 13:19 ` [PATCH v1 1/2] Documentation: process: Avoid unneeded Cc: tags Andy Shevchenko
2024-04-23 17:13   ` Dan Williams
2024-04-29  7:37   ` Krzysztof Kozlowski
2024-04-23 13:19 ` [PATCH v1 2/2] Documentation: process: Recommend to put Cc: tags after cutter '---' line Andy Shevchenko
2024-04-23 14:30   ` Jani Nikula
2024-04-23 14:37     ` Andy Shevchenko
2024-04-23 14:44       ` Jonathan Corbet
2024-04-23 16:46         ` Andy Shevchenko
2024-04-23 16:37       ` Jani Nikula
2024-04-23 16:45         ` Andy Shevchenko [this message]
2024-04-23 17:00           ` Jani Nikula
2024-04-23 17:04             ` Konstantin Ryabitsev
2024-04-23 15:26     ` Geert Uytterhoeven
2024-04-24  1:10     ` Mark Brown
2024-04-23 15:13   ` Greg KH
2024-04-23 15:28     ` Andy Shevchenko
2024-04-23 16:07       ` Greg KH
2024-04-23 16:12         ` Andy Shevchenko
2024-04-29  7:35   ` Krzysztof Kozlowski
2024-04-29  8:44     ` Andy Shevchenko
2024-04-23 13:59 ` [PATCH v1 0/2] Documentation: process: Clarify use of Cc: Geert Uytterhoeven
2024-04-24 14:53 ` Andy Shevchenko

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=Ziflr9ag4Nl2lTic@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=corbet@lwn.net \
    --cc=jani.nikula@intel.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=workflows@vger.kernel.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