Re: [RFC] Sending NILFS2 patches into upstream

[Ryusuke Konishi <konishi.ryusuke@gmail.com>]

On Fri, Nov 7, 2025 at 4:33 AM Viacheslav Dubeyko wrote:
>
> Hi Ryusuke,
>
> On Wed, 2025-11-05 at 15:44 +0900, Ryusuke Konishi wrote:
> > Hi Viacheslav,
> >
> > On Wed, Nov 5, 2025 at 5:10 AM Viacheslav Dubeyko wrote:
> > >
> > > Hi Ryusuke,
> > >
> > > On Tue, 2025-11-04 at 19:41 +0900, Ryusuke Konishi wrote:
> > > > On Tue, Nov 4, 2025 at 5:37 AM Viacheslav Dubeyko wrote:
> > > > >
> > > > > Hi Ryusuke,
> > > > >
> > > > > Currently, you ask Andrew Morton of sending NILFS2 patches into
> > > > > upstream. But Andrew is busy and it makes the whole workflow
> > > > > complicated and unpredictable.
> > > > >
> > > > > I am sending HFS/HFS+ patches to upstream. So, I can create the
> > > > > dedicated NILFS2 kernel tree on kernel.org and I can send
> > > > > NILFS2
> > > > > patches upstream. I believe that it can make the whole patch
> > > > > management
> > > > > workflow more flexible and predictable. Also, additional
> > > > > maintainer
> > > > > is
> > > > > better than to have only one.
> > > > >
> > > > > We already had some discussion privately. So, let's continue
> > > > > the
> > > > > discussion in the email list. What do you think?
> > > > >
> > > > > Thanks,
> > > > > Slava.
> > > >
> > > > Hi Viacheslav,
> > > >
> > > > Yes, thanks for the suggestion.
> > > >
> > > > As I replied to you privately earlier, I'd welcome your help both
> > > > with
> > > > upstreaming and setting up the git tree on kernel.org.
> > > >
> > > > First, I'll start by adding you as a maintainer.
> > > > To do this, I'd like to send a patch with changes to the
> > > > maintainers
> > > > file to Andrew.
> > >
> > > Sounds good! Probably, I can create the NILFS2 kernel tree on
> > > kernel.org at first. And, then this patch can be sent with adding
> > > the
> > > link to this kernel tree into MAINTAINERS file.
> >
> > Yes, it's OK to set up a git repository first.
> > In that case, we will only need to make the changes to the
> > MAINTAINERS
> > file once, so I'll send one patch for the next merge window.
> >
> > Not only do we add an M: field and switch the T: field, but the S:
> > field in the MAINTAINERS file should also be updated to reflect the
> > current status, so I'll make these changes all at once.
> >
> > Please let me know where the repository is once you've set it up.
> >
> > >
>
> I've created the repository today:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/vdubeyko/nilfs2.git
>
> And I've added two branches there:
>
> git branch --all
>   for-linus
> * for-next
>   master
>   remotes/origin/HEAD -> origin/master
>   remotes/origin/for-linus
>   remotes/origin/for-next
>   remotes/origin/master
>
> Thanks,
> Slava.

Thank you for setting up the git repository.

I just sent a patch with the MAINTAINERS changes, including that
location, so if you'd like, please send an Ack to Andrew as a reply.

Thanks,
Ryusuke Konishi