Searched refs:describe (Results 1 - 7 of 7) sorted by path

/seL4-camkes-master/projects/musllibc/tools/
H A Dversion.sh5 git describe --tags --match 'v[0-9]*' 2>/dev/null \
/seL4-camkes-master/projects/picotcp/docs/user_manual/
H A Duser_doc.tex82 The following sections will describe the API for picoTCP.
/seL4-camkes-master/tools/riscv-pk/scripts/
H A Dvcs-version.sh18 # The script uses git describe plus a few other git commands to create a
89 # See if we can do a describe based on a tag and if not use a default
92 if ( git describe --tags --match "rel-*" &> /dev/null ); then
93 ver_str=`git describe --tags --match "rel-*" | sed 's/rel-//'`
97 ver_sha=`git describe --tags --match "rel-*" --always`
/seL4-camkes-master/tools/rumprun/app-tools/
H A Drumprun-bake.in209 rumprun-bake [-c conffile ...] [-m cmd ...] describe config
214 "describe" outputs details for the given config.
333 if [ "${TARGET}" = "describe" ]; then
348 if [ "${TARGET}" = "describe" ]; then
349 [ $# -eq 2 ] || _die \"describe\" needs exactly one config.
/seL4-camkes-master/
H A Dgriddle123 describe () { function
261 describe "comment line"
264 describe "blank line"
267 describe "configuration variable: \"$LINE\""
299 describe "exporting external setting: \"$LINE\""
/seL4-camkes-master/tools/cogent/cogent/manual/
H A Dcogent-manual.tex513 currying, is illegal in \cogent. Strictly speaking, function types always describe unary functions. To specify the corresponding type
1648 \todo{describe all operation semantics and inferred types}
/seL4-camkes-master/tools/seL4/cmake-tool/
H A Dgriddle123 describe () { function
261 describe "comment line"
264 describe "blank line"
267 describe "configuration variable: \"$LINE\""
299 describe "exporting external setting: \"$LINE\""

Completed in 106 milliseconds