74f16b0c6f
All of these violations are necessary parts of the tests
(which are generally checking the behavior of trailing
whitespace, or contain diff fragments with empty lines).
Our solution is two-fold:
1. Process input with whitespace problems using tr. This
has the added bonus that it becomes very obvious where
the bogus whitespace is intended to go.
2. Move large diff fragments into their own supplemental
files. This gets rid of the whitespace problem, since
supplemental files are not checked, and it also makes
the test script a bit easier to read.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
31 lines
456 B
Diff
31 lines
456 B
Diff
diff --git a/main.c b/main.c
|
|
--- a/main.c
|
|
+++ b/main.c
|
|
@@ -1,13 +1,14 @@
|
|
#include <stdio.h>
|
|
|
|
int func(int num);
|
|
-void print_int(int num);
|
|
+int func2(int num);
|
|
|
|
int main() {
|
|
int i;
|
|
|
|
for (i = 0; i < 10; i++) {
|
|
- print_int(func(i));
|
|
+ printf("%d", func(i));
|
|
+ printf("%d", func3(i));
|
|
}
|
|
|
|
return 0;
|
|
@@ -17,7 +18,7 @@
|
|
return num * num;
|
|
}
|
|
|
|
-void print_int(int num) {
|
|
- printf("%d", num);
|
|
+int func2(int num) {
|
|
+ return num * num * num;
|
|
}
|
|
|