sequencer.c: avoid empty statements at top level
The macro GIT_PATH_FUNC expands to a function definition that ends with a closing brace. Remove two extra semicolons. While at it, fix the example in path.h. Signed-off-by: Beat Bolli <dev+git@drbeat.li> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Beat Bolli committed
Jul 9, 2018 at 21:25 UTC
9ad36356dd13b53667a51020c9aef0d4e014af01
2 files changed
+3
-3
path.h
+1
-1
@@ -147,7 +147,7 @@ extern void report_linked_checkout_garbage(void);
147
/*
148
* You can define a static memoized git path like:
149
*
150
- * static GIT_PATH_FUNC(git_path_foo, "FOO");
150
+ * static GIT_PATH_FUNC(git_path_foo, "FOO")
151
*
152
* or use one of the global ones below.
153
*/
sequencer.c
+2
-2
@@ -61,12 +61,12 @@ static GIT_PATH_FUNC(rebase_path_done, "rebase-merge/done")
61
* The file to keep track of how many commands were already processed (e.g.
62
* for the prompt).
63
*/
64
-static GIT_PATH_FUNC(rebase_path_msgnum, "rebase-merge/msgnum");
64
+static GIT_PATH_FUNC(rebase_path_msgnum, "rebase-merge/msgnum")
65
/*
66
* The file to keep track of how many commands are to be processed in total
67
* (e.g. for the prompt).
68
*/
69
-static GIT_PATH_FUNC(rebase_path_msgtotal, "rebase-merge/end");
69
+static GIT_PATH_FUNC(rebase_path_msgtotal, "rebase-merge/end")
70
/*
71
* The commit message that is planned to be used for any changes that
72
* need to be committed following a user interaction.