All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Sebastian Duda <sebastian.duda@fau.de>
Cc: "Pali Rohár" <pali.rohar@gmail.com>,
	linux-kernel@vger.kernel.org, lukas.bulwahn@gmail.com
Subject: Re: Status of Subsystems
Date: Tue, 20 Aug 2019 13:15:50 -0400	[thread overview]
Message-ID: <20190820171550.GE10232@mit.edu> (raw)
In-Reply-To: <3cf18665-7669-a33c-a718-e0917fa6d1b9@fau.de>

On Tue, Aug 20, 2019 at 03:56:24PM +0200, Sebastian Duda wrote:
> 
> so the status of the files is inherited from the subsystem `INPUT MULTITOUCH
> (MT) PROTOCOL`?
> 
> Is it the same with the subsystem `NOKIA N900 POWER SUPPLY DRIVERS`
> (respectively `POWER SUPPLY CLASS/SUBSYSTEM and DRIVERS`)?

Note that the definitions of "subsystems" is not necessarily precise.
So assuming there is a strict subclassing and inheritance might not be
a perfect assumption.  There are some files which have no official
owner, and there are also some files which may be modified by more
than one subsystem.

We certainly don't talk about "inheritance" when we talk about
maintainers and sub-maintainers.  Furthermore, the relationships,
processes, and workflows between a particular maintainer and their
submaintainers can be unique to a particular maintainer.

We define these terms to be convenient for Linux development, and like
many human institutions, they can be flexible and messy.  The goal was
*not* define things so it would be convenient for academics writing
papers --- like insects under glass.

Cheers,

						- Ted


  parent reply	other threads:[~2019-08-20 17:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-20 13:05 Status of Subsystems Sebastian Duda
2019-08-20 13:14 ` Pali Rohár
2019-08-20 13:56   ` Sebastian Duda
2019-08-20 14:05     ` Pali Rohár
2019-08-20 14:09     ` Joe Perches
2019-08-20 17:15     ` Theodore Y. Ts'o [this message]
2019-08-21 12:10       ` Enrico Weigelt, metux IT consult
2019-08-22 10:54         ` Sebastian Duda
2019-08-22 14:08         ` Theodore Y. Ts'o
2019-08-22  9:28       ` Sebastian Duda
2019-08-22 12:49         ` Enrico Weigelt, metux IT consult

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=20190820171550.GE10232@mit.edu \
    --to=tytso@mit.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukas.bulwahn@gmail.com \
    --cc=pali.rohar@gmail.com \
    --cc=sebastian.duda@fau.de \
    /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.