All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Peter Senna Tschudin <peter.senna@gmail.com>
Cc: joe@perches.com, gregkh@linuxfoundation.org, davem@davemloft.net,
	arnd@arndb.de, elezegarcia@gmail.com, Julia.Lawall@lip6.fr,
	linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH RFC] MAINTAINERS: Add section for subsystem shortname
Date: Tue, 02 Oct 2012 12:14:43 +0000	[thread overview]
Message-ID: <20121002121443.GT4587@mwanda> (raw)
In-Reply-To: <1349179024-5319-1-git-send-email-peter.senna@gmail.com>

On Tue, Oct 02, 2012 at 01:57:04PM +0200, Peter Senna Tschudin wrote:
> The shortname for a subsystem, that is primarly used when sending patches over E-mail, is not stored anywhere in the source code. Actually one need to dig git log or mailing list archives. There is no standard, and the Maintainer choose how to short name his/her subsystem. MAINTAINERS file is the right place for storing this information.
> 
> U is the second letter of Subsystem.
> 
> This will also enable automatic tools like scripts/get_maintainer.pl to provide the correct short name for each filename in the Kernel source tree.
> 

This is pretty useless without a script to parse it.  Also none of
subsystem names you chose as examples are correct.  Please line wrap
your commit message at 72 characters.

regards,
dan carpenter


WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Peter Senna Tschudin <peter.senna@gmail.com>
Cc: joe@perches.com, gregkh@linuxfoundation.org, davem@davemloft.net,
	arnd@arndb.de, elezegarcia@gmail.com, Julia.Lawall@lip6.fr,
	linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH RFC] MAINTAINERS: Add section for subsystem shortname
Date: Tue, 2 Oct 2012 15:14:43 +0300	[thread overview]
Message-ID: <20121002121443.GT4587@mwanda> (raw)
In-Reply-To: <1349179024-5319-1-git-send-email-peter.senna@gmail.com>

On Tue, Oct 02, 2012 at 01:57:04PM +0200, Peter Senna Tschudin wrote:
> The shortname for a subsystem, that is primarly used when sending patches over E-mail, is not stored anywhere in the source code. Actually one need to dig git log or mailing list archives. There is no standard, and the Maintainer choose how to short name his/her subsystem. MAINTAINERS file is the right place for storing this information.
> 
> U is the second letter of Subsystem.
> 
> This will also enable automatic tools like scripts/get_maintainer.pl to provide the correct short name for each filename in the Kernel source tree.
> 

This is pretty useless without a script to parse it.  Also none of
subsystem names you chose as examples are correct.  Please line wrap
your commit message at 72 characters.

regards,
dan carpenter


  reply	other threads:[~2012-10-02 12:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-02 11:57 [PATCH RFC] MAINTAINERS: Add section for subsystem shortname Peter Senna Tschudin
2012-10-02 11:57 ` Peter Senna Tschudin
2012-10-02 12:14 ` Dan Carpenter [this message]
2012-10-02 12:14   ` Dan Carpenter
2012-10-02 12:33   ` Peter Senna Tschudin
2012-10-02 12:33     ` Peter Senna Tschudin
2012-10-02 12:40     ` Ezequiel Garcia
2012-10-02 12:40       ` Ezequiel Garcia
2012-10-02 12:53       ` Peter Senna Tschudin
2012-10-02 12:53         ` Peter Senna Tschudin
2012-10-02 13:08         ` Ezequiel Garcia
2012-10-02 13:08           ` Ezequiel Garcia
2012-10-02 13:13           ` Peter Senna Tschudin
2012-10-02 13:13             ` Peter Senna Tschudin
2012-10-02 13:48             ` Joe Perches
2012-10-02 13:48               ` Joe Perches

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=20121002121443.GT4587@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=Julia.Lawall@lip6.fr \
    --cc=arnd@arndb.de \
    --cc=davem@davemloft.net \
    --cc=elezegarcia@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=joe@perches.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter.senna@gmail.com \
    /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.