Re: [PATCH 07/12] docs: accounting: update delay-accounting.rst reference
From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Date: 2021-06-02 20:19:51
Also in:
lkml
Em Wed, 2 Jun 2021 20:29:23 +0200 Peter Zijlstra [off-list ref] escreveu:
quoted
Peter Zijlstra [off-list ref] escreveu:quoted
On Wed, Jun 02, 2021 at 05:43:13PM +0200, Mauro Carvalho Chehab wrote:quoted
quoted
quoted
Enables/disables task delay accounting (see -:doc:`accounting/delay-accounting.rst`). Enabling this feature incurs +:doc:`/accounting/delay-accounting`). Enabling this feature incursThis breaks any chance of using 'goto file' like features in text editors :/This is a feature of your favorite text editor. Not all have it.Afaict both vim (gf) and emacs (M-x ffap) can do this. That covers about 99% of all sane editors no? :-)
Heh, not quite ;-) Here, I use nano(/pico), from the old times where (al)pine was my emailer. I can live with vim, but I prefer an editor that starts in editing mode. I tried to use emacs a few times, but my fingers are too much into pico/nano control keys, so it was ending by making me typing a lot slower. Besides that, nano works well on 99% of my daily needs. When I need more fancy, like regex substitutions, changing/moving big code blocks, editing multiple files at the same time, etc, then I just use a GUI editor (currently kate, but seeking for a good replacement, as some changes during F33 times - still present on F34 - caused some regressions). Em Wed, 02 Jun 2021 12:36:05 -0600 Jonathan Corbet [off-list ref] escreveu:
quoted
That's said, automarkup.py has a rule to convert Documentation/<foo>.rst into :doc:`<foo>`. So, an alternative approach would be to convert treewide all :doc:`<foo>` into Documentation/<foo>.rst and add something at checkpatch.pl to recommend to avoid :doc: notation.That seems like the right approach to me. We have the automarkup capability, we might as well make use of it...
Ok, I'll prepare a separate patch series addressing it. - Jon, With regards to the :doc: -> Documentation/ conversion, I guess I'll do it on an independent patch series against your docs-next tree. Then, I'll send a separate patch series after 5.14-rc1 in order to address the stuff under linux-next. Thanks, Mauro