lkml.org 
[lkml]   [2024]   [Apr]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH v1 2/2] Documentation: process: Recommend to put Cc: tags after cutter '---' line
On Tue, Apr 23, 2024 at 05:30:49PM +0300, Jani Nikula wrote:
> On Tue, 23 Apr 2024, Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:
> > The recommendation is based on the following rationale:
> >
> > - it makes the commit messages much cleaner and easy to read, especially
> > on the screens of the mobile devices;
> >
> > - it reduces resources (memory, time, energy) to retrieve all these
> > headers, which are barely needed by a mere user, as for automation
> > they will be still available via mail archives, such as
> > https://lore.kernel.org, assuming the Link: or Message-ID tag is
> > provided.
>
> I find the information in the commit message useful, and it tells me who
> were explicitly included in the discussion.
>
> For example when fixing a regression I'd like to Cc everyone who was
> Cc'd in the regressing commit. The drm subsystem maintainer tool
> actually has a helper for doing just that. 'dim fixes <sha1>' digs up
> all the relevant info.

> 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.

> A lot of patches get sent with
> more Cc's in the mail message than in the commit message.

Note, this is the recommendation as it's stated. You can continue polluting
the environment on your wish.

> > Let's be environment friendly and save the planet!

--
With Best Regards,
Andy Shevchenko



\
 
 \ /
  Last update: 2024-05-27 17:58    [W:1.039 / U:0.072 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site