Messages in this thread |  | | From | Miguel Ojeda <> | | Date | Tue, 5 May 2026 02:20:45 +0200 | | Subject | Re: [PATCH 8/9] docs: maintainers_include: don't ignore invalid profile entries |
| |
On Tue, May 5, 2026 at 2:08 AM Mauro Carvalho Chehab <mchehab+huawei@kernel.org> wrote: > > Also, with time, maintainers may change their employers while still > keeping their maintainership status. > > So, I'd say that whatever is there at the "P" entry, or where it is > located (either on a ReST file at the Kernel or on some external URL), > it should reflect the model that a maintainer or subsystem community > that actively participate at the Kernel development agrees with. > This should be vendor-agnostic.
I am not sure what you mean. By "vendored" I don't mean companies/employers, I mean that the file comes from an upstream repository:
https://github.com/Rust-for-Linux/pin-init/blob/main/CONTRIBUTING.md
Nevertheless, it is true that this really is a special case, in that the upstream project decided to provide something that could then be fit into the `P:` field.
One could say "let's ask them to do rst upstream", but to be honest, it is simpler to just put a hyperlink to GitHub's rendered file. Markdown is anyway a better fit for their file.
> Generating on the fly is a bad idea, as when one uses: > > make O=SOME_DIR > > It is expected that the original source directory will remain > untouched.
I am not sure why that would be a problem -- the output would be in `objtree`, not in `srctree`, as usual.
> I suggested pandoc as a one-time conversion if one wants to migrate > from MD to rst, as for simple documents like this one, it works > fine.
They are the maintainers, so it is up to them, but it is simpler to use a hyperlink.
(The file is trivial, i.e. the conversion can be done in a moment without `pandoc`).
Cheers, Miguel
|  |