From: Viacheslav Dubeyko <slava@dubeyko.com>
To: Yangtao Li <frank.li@vivo.com>,
Viacheslav Dubeyko <Slava.Dubeyko@ibm.com>,
"glaubitz@physik.fu-berlin.de" <glaubitz@physik.fu-berlin.de>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: update location of hfs&hfsplus trees
Date: Fri, 08 Aug 2025 12:50:47 -0700 [thread overview]
Message-ID: <a7857b101a09c1926d69f24076231f38cf5cde96.camel@dubeyko.com> (raw)
In-Reply-To: <c17cd9f3-0651-49ce-805f-d94ef2b232c1@vivo.com>
On Wed, 2025-08-06 at 00:43 +0800, Yangtao Li wrote:
> Hi Slava,
>
> 在 7/30/2025 3:12 AM, Viacheslav Dubeyko 写道:
> > On Tue, 2025-07-29 at 10:01 -0600, Yangtao Li wrote:
> > > Update it at MAINTAINERS file.
> > >
> > > Signed-off-by: Yangtao Li <frank.li@vivo.com>
> > > ---
> > > MAINTAINERS | 2 ++
> > > 1 file changed, 2 insertions(+)
> > >
> > > diff --git a/MAINTAINERS b/MAINTAINERS
> > > index 7a4e63bacaa4..48b25f1e2c01 100644
> > > --- a/MAINTAINERS
> > > +++ b/MAINTAINERS
> > > @@ -10659,6 +10659,7 @@ M: John Paul Adrian Glaubitz
> > > <glaubitz@physik.fu-berlin.de>
> > > M: Yangtao Li <frank.li@vivo.com>
> > > L: linux-fsdevel@vger.kernel.org
> > > S: Maintained
> > > +T: git
> > > git://git.kernel.org/pub/scm/linux/kernel/git/vdubeyko/hfs.git
> > > F: Documentation/filesystems/hfs.rst
> > > F: fs/hfs/
> > >
> > > @@ -10668,6 +10669,7 @@ M: John Paul Adrian Glaubitz
> > > <glaubitz@physik.fu-berlin.de>
> > > M: Yangtao Li <frank.li@vivo.com>
> > > L: linux-fsdevel@vger.kernel.org
> > > S: Maintained
> > > +T: git
> > > git://git.kernel.org/pub/scm/linux/kernel/git/vdubeyko/hfs.git
> > > F: Documentation/filesystems/hfsplus.rst
> > > F: fs/hfsplus/
> > >
> > Makes sense. We need to update it here.
> >
> > By the way, we have also [1]. I am collecting patches there at
> > first too and we
> > can use it for the initial testing. Also, we have very simple bug
> > tracking
> > system [2] and I am tracking the known and opened issues there.
> > Should we add
> > this information too?
> >
> > We have empty WiKi there, but we could add the information there
> > too.
>
>
> Do you mind we add those facility step by step, or add those facility
> in
> one patch?
>
>
I think it makes sense to have all info in one patch. What's the point
to split it on several patches?
Thanks,
Slava.
prev parent reply other threads:[~2025-08-08 19:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 16:01 Yangtao Li
2025-07-29 19:12 ` Viacheslav Dubeyko
2025-08-05 16:43 ` Yangtao Li
2025-08-08 19:50 ` Viacheslav Dubeyko [this message]
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=a7857b101a09c1926d69f24076231f38cf5cde96.camel@dubeyko.com \
--to=slava@dubeyko.com \
--cc=Slava.Dubeyko@ibm.com \
--cc=frank.li@vivo.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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®