9cba13ca5d
In a struct definitions, unlike functions, the prevailing style is for
the opening brace to go on the same line as the struct name, like so:
struct foo {
int bar;
char *baz;
};
Indeed, grepping for 'struct [a-z_]* {$' yields about 5 times as many
matches as 'struct [a-z_]*$'.
Linus sayeth:
Heretic people all over the world have claimed that this inconsistency
is ... well ... inconsistent, but all right-thinking people know that
(a) K&R are _right_ and (b) K&R are right.
Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
24 lines
443 B
Bash
Executable File
24 lines
443 B
Bash
Executable File
#!/bin/sh
|
|
|
|
echo "/* Automatically generated by $0 */
|
|
struct cmdname_help {
|
|
char name[16];
|
|
char help[80];
|
|
};
|
|
|
|
static struct cmdname_help common_cmds[] = {"
|
|
|
|
sed -n -e 's/^git-\([^ ]*\)[ ].* common.*/\1/p' command-list.txt |
|
|
sort |
|
|
while read cmd
|
|
do
|
|
sed -n '
|
|
/^NAME/,/git-'"$cmd"'/H
|
|
${
|
|
x
|
|
s/.*git-'"$cmd"' - \(.*\)/ {"'"$cmd"'", "\1"},/
|
|
p
|
|
}' "Documentation/git-$cmd.txt"
|
|
done
|
|
echo "};"
|