On Wed, 4 Oct 2017 20:36:42 +0200, Jesper Dangaard Brouer wrote: > On Wed, 4 Oct 2017 08:40:32 -0700 > Jakub Kicinski <jakub.kicinski@xxxxxxxxxxxxx> wrote: > > > Add documentation for bpftool. Separate files for each subcommand. > > Use rst format. Documentation is compiled into man pages using > > rst2man. > > > > Signed-off-by: David Beckett <david.beckett@xxxxxxxxxxxxx> > > Signed-off-by: Jakub Kicinski <jakub.kicinski@xxxxxxxxxxxxx> > > Acked-by: Alexei Starovoitov <ast@xxxxxxxxxx> > > Acked-by: Daniel Borkmann <daniel@xxxxxxxxxxxxx> > > --- > > tools/bpf/bpftool/Documentation/Makefile | 34 +++++++ > > tools/bpf/bpftool/Documentation/bpftool-map.txt | 110 +++++++++++++++++++++++ > > tools/bpf/bpftool/Documentation/bpftool-prog.txt | 79 ++++++++++++++++ > > tools/bpf/bpftool/Documentation/bpftool.txt | 34 +++++++ > > RST-format files are usually called .rst and not .txt > > This is useful when people happen to browse the code via github, then they get formatted nicely e.g.: > https://github.com/torvalds/linux/blob/master/samples/bpf/README.rst I was following perf's example. Are perf's docs not RST? -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
