Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1645653
| From | Masami Hiramatsu <mhiramat@kernel.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH 11/30] kprobes.txt: standardize document format |
| Date | 2017-05-19 16:40 +0200 |
| Message-ID | <tIReq-3xO-13@gated-at.bofh.it> (permalink) |
| References | <tIETU-39a-23@gated-at.bofh.it> <tIF3C-3cN-69@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Thu, 18 May 2017 22:24:03 -0300 Mauro Carvalho Chehab <mchehab@s-opensource.com> wrote: > Each text file under Documentation follows a different > format. Some doesn't even have titles! > > Change its representation to follow the adopted standard, > using ReST markups for it to be parseable by Sphinx: > > - comment the contents; > - add proper markups for titles; > - mark literal blocks as such; > - use :Author: for authorship; > - use the right markups for footnotes; > - escape some literals that would otherwise cause problems; > - fix identation and add blank lines where needed. OK, it seems good to me. Acked-by: Masami Hiramatsu <mhiramat@kernel.org> By the way, there are some words which referes other section in this document, should it also be updated according to Sphinx format? e.g. [snip] > @@ -53,7 +59,8 @@ a post_handler, and how to use the maxactive and nmissed fields of > a kretprobe. But if you're in a hurry to start using Kprobes, you > can skip ahead to section 2. here, it refers "section 2". Thank you, -- Masami Hiramatsu <mhiramat@kernel.org>
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
[PATCH 11/30] kprobes.txt: standardize document format Mauro Carvalho Chehab <mchehab@s-opensource.com> - 2017-05-19 03:40 +0200 Re: [PATCH 11/30] kprobes.txt: standardize document format Masami Hiramatsu <mhiramat@kernel.org> - 2017-05-19 16:40 +0200
csiph-web