Add a note that explains that Cc: email header is implied by other
tags, such as Reviewed-by:. In this case an explicit Cc: is _not_
needed.
Signed-off-by: Andy Shevchenko
---
Documentation/process/5.Posting.rst | 4 +++-
Documentation/process/submitting-patches.rst | 5 -
2 files
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 au
Add a couple of recommendations on how to utilise Cc header in
environment friendly way.
Andy Shevchenko (2):
Documentation: process: Avoid unneeded Cc: tags
Documentation: process: Recommend to put Cc: tags after cutter '---'
line
Documentation/process/5.Posting.rst | 8 ++
On Tue, Apr 23, 2024 at 3:21 PM Andy Shevchenko
wrote:
> Add a couple of recommendations on how to utilise Cc header in
> environment friendly way.
Acked-by: Geert Uytterhoeven
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge..
On Tue, 23 Apr 2024, Andy Shevchenko 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
> h
On Tue, Apr 23, 2024 at 05:30:49PM +0300, Jani Nikula wrote:
> On Tue, 23 Apr 2024, Andy Shevchenko
> 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;
> >
Andy Shevchenko writes:
>> 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.
The environmental case here is ... not strong.
I, too, have my d
On Tue, Apr 23, 2024 at 04:19:38PM +0300, Andy Shevchenko 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;
Reading commits on a mobile device is not what kernel d
Hi Jani,
On Tue, Apr 23, 2024 at 4:31 PM Jani Nikula wrote:
> On Tue, 23 Apr 2024, Andy Shevchenko
> 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;
>
On Tue, Apr 23, 2024 at 08:13:37AM -0700, Greg KH wrote:
> On Tue, Apr 23, 2024 at 04:19:38PM +0300, Andy Shevchenko 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 mobil
On Tue, Apr 23, 2024 at 06:28:44PM +0300, Andy Shevchenko wrote:
> On Tue, Apr 23, 2024 at 08:13:37AM -0700, Greg KH wrote:
> > On Tue, Apr 23, 2024 at 04:19:38PM +0300, Andy Shevchenko wrote:
> > > The recommendation is based on the following rationale:
> > >
> > > - it makes the commit messages
On Tue, Apr 23, 2024 at 09:07:09AM -0700, Greg KH wrote:
> On Tue, Apr 23, 2024 at 06:28:44PM +0300, Andy Shevchenko wrote:
> > On Tue, Apr 23, 2024 at 08:13:37AM -0700, Greg KH wrote:
> > > On Tue, Apr 23, 2024 at 04:19:38PM +0300, Andy Shevchenko wrote:
> > > > The recommendation is based on the
On Tue, 23 Apr 2024, Andy Shevchenko 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 C
On Tue, Apr 23, 2024 at 07:37:34PM +0300, Jani Nikula wrote:
> On Tue, 23 Apr 2024, Andy Shevchenko
> 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.
>
On Tue, Apr 23, 2024 at 08:44:24AM -0600, Jonathan Corbet wrote:
> Andy Shevchenko writes:
>
> >> 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 o
On Tue, 23 Apr 2024, Andy Shevchenko wrote:
> On Tue, Apr 23, 2024 at 07:37:34PM +0300, Jani Nikula wrote:
>> On Tue, 23 Apr 2024, Andy Shevchenko
>> 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 n
On Tue, Apr 23, 2024 at 08:00:16PM +0300, Jani Nikula wrote:
> Imagine the commit message Cc was named "Attn:" and handled
> appropriately. That probably reflects a lot of commit message Cc
> usage.
This is especially the case for get_maintainer.pl purposes. Adding a Cc:
in a commit message mean
Andy Shevchenko wrote:
> Add a note that explains that Cc: email header is implied by other
> tags, such as Reviewed-by:. In this case an explicit Cc: is _not_
> needed.
>
> Signed-off-by: Andy Shevchenko
> ---
> Documentation/process/5.Posting.rst | 4 +++-
> Documentation/process/sub
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. A lot of patches get sent with
> more Cc's in the mail message than in the commit message.
These days with b4 and lore it
19 matches
Mail list logo
