All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Sasha Levin <sashal@kernel.org>
Cc: stable@vger.kernel.org
Subject: Re: MAINTAINERS updates in stable trees
Date: Sat, 7 Dec 2019 12:45:17 +0100	[thread overview]
Message-ID: <20191207114517.GA323212@kroah.com> (raw)
In-Reply-To: <20191207023802.GY5861@sasha-vm>

On Fri, Dec 06, 2019 at 09:38:02PM -0500, Sasha Levin wrote:
> I just saw an update to the MAINTAINERS file fly by on stable@ and
> figured we might want to be grabbing all of those into our stable trees?
> 
> Unlike documentation, it's not something the case that it can diverge
> from the code, and it's also very unlikely that someone wants to keep
> recieving mails as a result of someone who runs get_maintainers.pl on
> older kernels after he has removed his name upstream.
> 
> Any objections to taking these updates? It'll grow our patch count, but
> that's one of the rare cases where I don't see a way for it to cause
> regressions...

It's going to be a hodge-podge of acceptance and non acceptance here,
and in reality, it doesn't matter at all.  MAINTAINERS is to list where
to send problems to for the current development tree, not for the stable
trees.  So it's not going to be good to try to keep something up to date
when you need to make a patch against the development tree anyway.

Also, you will end up with file patterns and such getting out of date
and not matching up over time with older kernels, so I would just ignore
these entirely.

thanks,

greg k-h

      reply	other threads:[~2019-12-07 11:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-07  2:38 MAINTAINERS updates in stable trees Sasha Levin
2019-12-07 11:45 ` Greg KH [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=20191207114517.GA323212@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=sashal@kernel.org \
    --cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.