Searched refs:markup (Results 51 – 67 of 67) sorted by relevance
123
/openbmc/openbmc/poky/meta/files/common-licenses/ |
H A D | GFDL-1.1-only | 28 …xt formatters. A copy made in an otherwise Transparent file format whose markup has been designed … 30 Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo inp…
|
H A D | GFDL-1.1-no-invariants-or-later | 28 …xt formatters. A copy made in an otherwise Transparent file format whose markup has been designed … 30 Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo inp…
|
H A D | GFDL-1.1-invariants-or-later | 28 …xt formatters. A copy made in an otherwise Transparent file format whose markup has been designed … 30 Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo inp…
|
H A D | GFDL-1.1-or-later | 28 …xt formatters. A copy made in an otherwise Transparent file format whose markup has been designed … 30 Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo inp…
|
/openbmc/linux/Documentation/userspace-api/media/ |
H A D | fdl-appendix.rst | 98 file format whose markup has been designed to thwart or discourage 103 without markup, Texinfo input format, LaTeX input format, SGML or XML
|
/openbmc/openbmc/poky/meta/recipes-devtools/gcc/gcc/ |
H A D | 0016-handle-sysroot-support-for-nativesdk-gcc.patch | 18 a) Add %r into spec file markup which can be used for injected paths
|
/openbmc/openbmc/poky/documentation/migration-guides/ |
H A D | release-notes-4.2.4.rst | 97 - dev-manual: remove unsupported :term: markup inside markup
|
/openbmc/qemu/docs/devel/ |
H A D | qapi-code-gen.rst | 894 Documentation markup 897 Documentation comments can use most rST markup. In particular, 926 The usual ****strong****, *\*emphasized\** and ````literal```` markup 1011 text is formatted, and rST markup can be used.
|
/openbmc/webui-vue/docs/guide/components/table/ |
H A D | index.md | 155 with accessible markup and click handler
|
/openbmc/linux/Documentation/doc-guide/ |
H A D | kernel-doc.rst | 348 descriptive text and converted to proper reStructuredText markup and `Sphinx C
|
/openbmc/linux/Documentation/admin-guide/ |
H A D | spkguide.txt | 1304 format whose markup, or absence of markup, has been arranged to thwart 1310 ASCII without markup, Texinfo input format, LaTeX input format, SGML
|
/openbmc/linux/Documentation/process/ |
H A D | adding-syscalls.rst | 486 markup, but plain text will do. If groff is used, it's helpful to include a
|
H A D | howto.rst | 180 The documents that uses ReST markup will be generated at Documentation/output.
|
/openbmc/linux/Documentation/translations/sp_SP/process/ |
H A D | adding-syscalls.rst | 535 idealmente usando groff markup, pero texto plano también funciona. Si se
|
/openbmc/linux/Documentation/translations/sp_SP/ |
H A D | howto.rst | 178 Los documentos que utilizan el markup ReST se generarán en
|
/openbmc/openbmc/poky/meta/classes-global/ |
H A D | sstate.bbclass | 667 # clear where the symlink is relative to in this context. We could add that markup
|
/openbmc/entity-manager/ |
H A D | Doxyfile | 780 # markup commands wrongly.
|
123