mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Steve French" <smfrench@gmail.com>
To: "Andrew Bartlett" <abartlet@samba.org>
Cc: joe@perches.com, torvalds@linux-foundation.org,
	sfrench@samba.org, samba-technical@lists.samba.org,
	linux-kernel@vger.kernel.org, linux-cifs-client@lists.samba.org,
	akpm@linux-foundation.org
Subject: Re: [PATCH] [123/2many] MAINTAINERS - COMMON INTERNET FILE SYSTEM (CIFS)
Date: Mon, 13 Aug 2007 15:37:36 -0500	[thread overview]
Message-ID: <524f69650708131337i5f9f9761gea2600c1c1be3be7@mail.gmail.com> (raw)
In-Reply-To: <1187002400.22086.6.camel@dragonlady>

On 8/13/07, Andrew Bartlett <abartlet@samba.org> wrote:
> On Sun, 2007-08-12 at 23:25 -0700, joe@perches.com wrote:
> > Add file pattern to MAINTAINER entry
> >
> > Signed-off-by: Joe Perches <joe@perches.com>
> >
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index 1c014f1..5144e4e 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -1201,6 +1201,7 @@ L:      samba-technical@lists.samba.org
> >  W:   http://us1.samba.org/samba/Linux_CIFS_client.html
> >  T:   git kernel.org:/pub/scm/linux/kernel/git/sfrench/cifs-2.6.git
> >  S:   Supported
> > +F:   fs/cifs/
>
> No comment on the F:, but the L: entry here is interesting.  Is
> samba-technical really the right list for cifs-vfs patches?  Aside from
> being CC'ed on such patches, I've never seen discussion of them on the
> Samba mailing lists.
>
> Steve: Shouldn't that be linux-cifs-client?

linux-cifs-client is mentioned on the L: entry immediately before the
samba-technical one so no change seems to be needed for that.

I updated the W: line to point to the preferred URL
(http://linux-cifs.samba.org)

Adding an F: entry in the future is fine by me

-- 
Thanks,

Steve

  reply	other threads:[~2007-08-13 20:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-13  6:25 joe
2007-08-13 10:53 ` Andrew Bartlett
2007-08-13 20:37   ` Steve French [this message]
2007-08-13 15:09 ` Steve French

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=524f69650708131337i5f9f9761gea2600c1c1be3be7@mail.gmail.com \
    --to=smfrench@gmail.com \
    --cc=abartlet@samba.org \
    --cc=akpm@linux-foundation.org \
    --cc=joe@perches.com \
    --cc=linux-cifs-client@lists.samba.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=samba-technical@lists.samba.org \
    --cc=sfrench@samba.org \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®