Em Tue, 18 Oct 2016 09:07:03 +0300 Jani Nikula <jani.nikula@xxxxxxxxx> escreveu: > On Mon, 17 Oct 2016, Mauro Carvalho Chehab <mchehab@xxxxxxxxxxxxx> wrote: > > [PATCH] docs-rst: user: add MAINTAINERS > > > > including MAINTAINERS using ReST is tricky, because all > > maintainer's entries are like: > > > > FOO SUBSYSTEM: > > M: My Name <my@name> > > L: mailing@list > > S: Maintained > > F: foo/bar > > > > On ReST, this would be displayed on a single line. Using > > alias, like |M|, |L|, ... won't solve, as an alias in > > Sphinx doesn't accept breaking lines. > > > > So, instead of changing every line at MAINTAINERS, let's > > use kernel-cmd extension in order to parse it via a script. > > Soon I'm going to stop fighting the windmills... > > If you're going to insist on getting kernel-cmd upstream (and I haven't > changed my opinion on that) I also didn't change my mind that maintaining just one python script is easier than maintaining a plead of python scripts with almost identical contents. In any case, if we're willing to have one Python script per each different non-Python parser, it helps if the source code of such extensions would be identical, except for the command line that will run the script, as, if we find a bug on one such script, the same bug fix could be applied to the other almost identical ones. > please at least have the sense to have just > *one* perl script to parse MAINTAINERS, not many. The one script should > be scripts/get_maintainer.pl. Agreed. get_maintainer.pl is indeed the best place to put it. I wrote it this separate script just for a proof of concept, whose goal is to test if the kernel-cmd extension would be properly parsing the ReST output, and to identify what sort of output would fit best for the MAINTAINERS database. Thanks, Mauro -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
