Merge branch 'tz/doc-txt-to-adoc-fixes'
Fallouts from recent renaming of documentation files from .txt suffix to the new .adoc suffix have been corrected. * tz/doc-txt-to-adoc-fixes: (38 commits) xdiff: *.txt -> *.adoc fixes unpack-trees.c: *.txt -> *.adoc fixes transport.h: *.txt -> *.adoc fixes trace2/tr2_sysenv.c: *.txt -> *.adoc fixes trace2.h: *.txt -> *.adoc fixes t6434: *.txt -> *.adoc fixes t6012: *.txt -> *.adoc fixes t/helper/test-rot13-filter.c: *.txt -> *.adoc fixes simple-ipc.h: *.txt -> *.adoc fixes setup.c: *.txt -> *.adoc fixes refs.h: *.txt -> *.adoc fixes pseudo-merge.h: *.txt -> *.adoc fixes parse-options.h: *.txt -> *.adoc fixes object-name.c: *.txt -> *.adoc fixes list-objects-filter-options.h: *.txt -> *.adoc fixes fsck.h: *.txt -> *.adoc fixes diffcore.h: *.txt -> *.adoc fixes diff.h: *.txt -> *.adoc fixes contrib/long-running-filter: *.txt -> *.adoc fixes config.c: *.txt -> *.adoc fixes ...
This commit is contained in:
@ -9,9 +9,9 @@ people describing how they use Git in their workflow.
|
||||
|
||||
EOF
|
||||
|
||||
for txt
|
||||
for adoc
|
||||
do
|
||||
title=$(expr "$txt" : '.*/\(.*\)\.txt$')
|
||||
title=$(expr "$adoc" : '.*/\(.*\)\.adoc$')
|
||||
from=$(sed -ne '
|
||||
/^$/q
|
||||
/^From:[ ]/{
|
||||
@ -21,7 +21,7 @@ do
|
||||
s/^/by /
|
||||
p
|
||||
}
|
||||
' "$txt")
|
||||
' "$adoc")
|
||||
|
||||
abstract=$(sed -ne '
|
||||
/^Abstract:[ ]/{
|
||||
@ -39,13 +39,13 @@ do
|
||||
x
|
||||
p
|
||||
q
|
||||
}' "$txt")
|
||||
}' "$adoc")
|
||||
|
||||
if grep 'Content-type: text/asciidoc' >/dev/null $txt
|
||||
if grep 'Content-type: text/asciidoc' >/dev/null $adoc
|
||||
then
|
||||
file=$(expr "$txt" : '\(.*\)\.txt$').html
|
||||
file=$(expr "$adoc" : '\(.*\)\.adoc$').html
|
||||
else
|
||||
file="$txt"
|
||||
file="$adoc"
|
||||
fi
|
||||
|
||||
echo "* link:howto/$(basename "$file")[$title] $from
|
||||
|
@ -48,7 +48,7 @@ binary); this organization makes it easy for people reading the code
|
||||
to find things.
|
||||
|
||||
See the CodingGuidelines document for other guidance on what we consider
|
||||
good practice in C and shell, and api-builtin.txt for the support
|
||||
good practice in C and shell, and builtin.h for the support
|
||||
functions available to built-in commands written in C.
|
||||
|
||||
What every extension command needs
|
||||
|
Reference in New Issue
Block a user