lkml.org 
[lkml]   [2020]   [Mar]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] MAINTAINERS: adjust to filesystem doc ReST conversion
Em Wed, 4 Mar 2020 13:10:35 -0700
Jonathan Corbet <corbet@lwn.net> escreveu:

> On Wed, 4 Mar 2020 08:29:50 +0100
> Lukas Bulwahn <lukas.bulwahn@gmail.com> wrote:
>
> > Mauro's patch series <cover.1581955849.git.mchehab+huawei@kernel.org>
> > ("[PATCH 00/44] Manually convert filesystem FS documents to ReST")
> > converts many Documentation/filesystems/ files to ReST.
> >
> > Since then, ./scripts/get_maintainer.pl --self-test complains with 27
> > warnings on Documentation/filesystems/ of this kind:
> >
> > warning: no file matches F: Documentation/filesystems/...
> >
> > Adjust MAINTAINERS entries to all files converted from .txt to .rst in the
> > patch series and address the 27 warnings.
> >
> > Link: https://lore.kernel.org/linux-erofs/cover.1581955849.git.mchehab+huawei@kernel.org
> > Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> > ---
> > Mauro, please ack.
> > Jonathan, pick pick this patch for doc-next.
>
> Sigh, I need to work a MAINTAINERS check into my workflow...
>
> Thanks for fixing these, but ... what tree did you generate the patch
> against? I doesn't come close to applying to docs-next.

I'm starting to suspect that maybe the best workflow would be to just
apply the patches at docs-next keeping links broken, and then run
./scripts/documentation-file-ref-check --fix by the end of a merge
window, addressing such breakages.

There are usually lots of churn outside the merge window.

Another alternative would be to split the MAINTAINERS file on a
per-subsystem basis. If I remember well, someone proposed this once at
LKML. I vaguely remember that there were even a patch (or RFC)
adding support for such thing for get_maintainers.pl.

Thanks,
Mauro

\
 
 \ /
  Last update: 2020-03-04 21:29    [W:0.159 / U:3.508 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site