public inbox for linux-cifs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Namjae Jeon" <namjae.jeon@samsung.com>
To: "'Aurélien Aptel'" <aurelien.aptel@gmail.com>,
	"'Christoph Hellwig'" <hch@infradead.org>
Cc: <linux-cifsd-devel@lists.sourceforge.net>,
	<linux-cifs@vger.kernel.org>,
	"'Steve French'" <smfrench@gmail.com>,
	"'ronnie sahlberg'" <ronniesahlberg@gmail.com>
Subject: RE: ksmbd mailing list
Date: Wed, 23 Jun 2021 11:41:04 +0900	[thread overview]
Message-ID: <006501d767d9$361eeec0$a25ccc40$@samsung.com> (raw)
In-Reply-To: <87mtriqj6v.fsf@suse.com>

> "Namjae Jeon" <namjae.jeon@samsung.com> writes:
> > Add CC: Steve, Ronnie, Aurélien.
> > Any opinions?
> 
> I think having only one list would be nice too, but we should ask/document to put a [cifsd] tag
> somewhere in the subject, which is hard to enforce.
> 
> Case in point, it already gets confusing when people send patches for
> cifs-utils: we can't always tell it's not for the kernel from the subject which can confuse people and
> scripts.
Thanks for your opinion!
I will change to specify single list(linux-cifs@vger.kernel.org) in MAINTAINERS.

> Cheers,
> --
> Aurélien Aptel / SUSE Labs Samba Team
> GPG: 1839 CB5F 9F5B FB9B AA97  8C99 03C8 A49B 521B D5D3 SUSE Software Solutions Germany GmbH,
> Maxfeldstr. 5, 90409 Nürnberg, DE
> GF: Felix Imendörffer, Mary Higgins, Sri Rasiah HRB 247165 (AG München)



  reply	other threads:[~2021-06-23  2:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20210622061228epcas1p247d557ef24a971eaf395edd6174bed5e@epcas1p2.samsung.com>
2021-06-22  6:12 ` ksmbd mailing list 'Christoph Hellwig'
2021-06-22  6:58   ` Namjae Jeon
2021-06-22 10:37     ` Aurélien Aptel
2021-06-23  2:41       ` Namjae Jeon [this message]
2021-06-23  2:52         ` Steve French
2021-06-23  4:01           ` Namjae Jeon
2021-06-23  4:52           ` Christoph Hellwig
2021-06-23  5:04             ` Namjae Jeon

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='006501d767d9$361eeec0$a25ccc40$@samsung.com' \
    --to=namjae.jeon@samsung.com \
    --cc=aurelien.aptel@gmail.com \
    --cc=hch@infradead.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-cifsd-devel@lists.sourceforge.net \
    --cc=ronniesahlberg@gmail.com \
    --cc=smfrench@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox