Home
last modified time | relevance | path

Searched refs:markup (Results 51 – 67 of 67) sorted by relevance

123

/openbmc/openbmc/poky/meta/files/common-licenses/
H A DGFDL-1.1-only28 …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 DGFDL-1.1-no-invariants-or-later28 …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 DGFDL-1.1-invariants-or-later28 …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 DGFDL-1.1-or-later28 …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 Dfdl-appendix.rst98 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 D0016-handle-sysroot-support-for-nativesdk-gcc.patch18 a) Add %r into spec file markup which can be used for injected paths
/openbmc/openbmc/poky/documentation/migration-guides/
H A Drelease-notes-4.2.4.rst97 - dev-manual: remove unsupported :term: markup inside markup
/openbmc/qemu/docs/devel/
H A Dqapi-code-gen.rst894 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 Dindex.md155 with accessible markup and click handler
/openbmc/linux/Documentation/doc-guide/
H A Dkernel-doc.rst348 descriptive text and converted to proper reStructuredText markup and `Sphinx C
/openbmc/linux/Documentation/admin-guide/
H A Dspkguide.txt1304 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 Dadding-syscalls.rst486 markup, but plain text will do. If groff is used, it's helpful to include a
H A Dhowto.rst180 The documents that uses ReST markup will be generated at Documentation/output.
/openbmc/linux/Documentation/translations/sp_SP/process/
H A Dadding-syscalls.rst535 idealmente usando groff markup, pero texto plano también funciona. Si se
/openbmc/linux/Documentation/translations/sp_SP/
H A Dhowto.rst178 Los documentos que utilizan el markup ReST se generarán en
/openbmc/openbmc/poky/meta/classes-global/
H A Dsstate.bbclass667 # clear where the symlink is relative to in this context. We could add that markup
/openbmc/entity-manager/
H A DDoxyfile780 # markup commands wrongly.

123