All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Pavel Machek <pavel@suse.cz>
Cc: linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@osdl-foundation.org>,
	Randy Dunlap <randy.dunlap@oracle.com>,
	Uwe Kleine-K?nig <ukleinek@strlen.de>
Subject: Re: [PATCH 3/3] MAINTAINERS updates
Date: Tue, 21 Oct 2008 01:31:51 -0700	[thread overview]
Message-ID: <1224577912.12101.110.camel@localhost> (raw)
In-Reply-To: <20081021082623.GD15782@atrey.karlin.mff.cuni.cz>

On Tue, 2008-10-21 at 10:26 +0200, Pavel Machek wrote:
> >  AHA152X SCSI DRIVER
> >  P:	Juergen E. Fischer
> > -M:	Juergen Fischer <fischer@norbit.de>
> > +M:	fischer@norbit.de
> >  L:	linux-scsi@vger.kernel.org
> >  S:	Maintained
> >  F:	drivers/scsi/aha152x*
> >  F:	drivers/scsi/pcmcia/aha152x*
> 
> Actually I like the old style better. It makes copy & paste with mouse
> easy...

I'd prefer a merge of the P and M fields as well,
but didn't want to change that right now.

Consistent use of a single style will allow a script
to merge the fields easily.

cheers, Joe


  reply	other threads:[~2008-10-21  8:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-20 22:28 [PATCH 0/3] Add file patterns to MAINTAINERS and script to parse MAINTAINERS Joe Perches
2008-10-20 22:28 ` [PATCH 1/3] Add file patterns to MAINTAINERS Joe Perches
2008-10-20 22:28   ` [PATCH 2/3] Add a script to parse file pattern information in MAINTAINERS Joe Perches
2008-10-20 22:28     ` [PATCH 3/3] MAINTAINERS updates Joe Perches
2008-10-21  8:26       ` Pavel Machek
2008-10-21  8:31         ` Joe Perches [this message]
2008-10-20 22:50   ` [PATCH 1/3] Add file patterns to MAINTAINERS Dominik Brodowski
2008-10-20 23:02     ` Joe Perches
2008-10-20 23:45       ` Dominik Brodowski
2008-10-21  0:12         ` Joe Perches
2008-10-21  0:30           ` Dominik Brodowski
2008-10-21  1:58   ` Jeff Kirsher
2008-10-21  2:38     ` Joe Perches
2008-10-21  8:25   ` Pavel Machek

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=1224577912.12101.110.camel@localhost \
    --to=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    --cc=randy.dunlap@oracle.com \
    --cc=torvalds@osdl-foundation.org \
    --cc=ukleinek@strlen.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.