]>
Commit | Line | Data |
---|---|---|
6d0618a8 | 1 | Like other projects, we also have some guidelines to keep to the |
6c3b2afe | 2 | code. For Git in general, a few rough rules are: |
6d0618a8 JS |
3 | |
4 | - Most importantly, we never say "It's in POSIX; we'll happily | |
5 | ignore your needs should your system not conform to it." | |
6 | We live in the real world. | |
7 | ||
8 | - However, we often say "Let's stay away from that construct, | |
9 | it's not even in POSIX". | |
10 | ||
11 | - In spite of the above two rules, we sometimes say "Although | |
12 | this is not in POSIX, it (is so convenient | makes the code | |
13 | much more readable | has other good characteristics) and | |
14 | practically all the platforms we care about support it, so | |
15 | let's use it". | |
16 | ||
17 | Again, we live in the real world, and it is sometimes a | |
18 | judgement call, the decision based more on real world | |
19 | constraints people face than what the paper standard says. | |
20 | ||
dd30800b JH |
21 | - Fixing style violations while working on a real change as a |
22 | preparatory clean-up step is good, but otherwise avoid useless code | |
23 | churn for the sake of conforming to the style. | |
24 | ||
25 | "Once it _is_ in the tree, it's not really worth the patch noise to | |
26 | go and fix it up." | |
2e477d8d | 27 | Cf. http://lkml.iu.edu/hypermail/linux/kernel/1001.3/01069.html |
dd30800b | 28 | |
607817a3 JH |
29 | - Log messages to explain your changes are as important as the |
30 | changes themselves. Clearly written code and in-code comments | |
31 | explain how the code works and what is assumed from the surrounding | |
32 | context. The log messages explain what the changes wanted to | |
33 | achieve and why the changes were necessary (more on this in the | |
34 | accompanying SubmittingPatches document). | |
35 | ||
c5e366b1 | 36 | Make your code readable and sensible, and don't try to be clever. |
6d0618a8 JS |
37 | |
38 | As for more concrete guidelines, just imitate the existing code | |
39 | (this is a good guideline, no matter which project you are | |
dfb047b9 | 40 | contributing to). It is always preferable to match the _local_ |
2de9b711 | 41 | convention. New code added to Git suite is expected to match |
dfb047b9 NS |
42 | the overall style of existing code. Modifications to existing |
43 | code is expected to match the style the surrounding code already | |
44 | uses (even if it doesn't match the overall style of existing code). | |
45 | ||
7a06a854 CG |
46 | But if you must have a list of rules, here are some language |
47 | specific ones. Note that Documentation/ToolsForGit.txt document | |
48 | has a collection of tips to help you use some external tools | |
49 | to conform to these guidelines. | |
6d0618a8 JS |
50 | |
51 | For shell scripts specifically (not exhaustive): | |
52 | ||
f36a4fa8 GB |
53 | - We use tabs for indentation. |
54 | ||
79fc3ca1 JH |
55 | - Case arms are indented at the same depth as case and esac lines, |
56 | like this: | |
57 | ||
58 | case "$variable" in | |
59 | pattern1) | |
60 | do this | |
61 | ;; | |
62 | pattern2) | |
63 | do that | |
64 | ;; | |
65 | esac | |
f36a4fa8 | 66 | |
48f359bf TH |
67 | - Redirection operators should be written with space before, but no |
68 | space after them. In other words, write 'echo test >"$file"' | |
69 | instead of 'echo test> $file' or 'echo test > $file'. Note that | |
70 | even though it is not required by POSIX to double-quote the | |
71 | redirection target in a variable (as shown above), our code does so | |
72 | because some versions of bash issue a warning without the quotes. | |
73 | ||
6a49909b JH |
74 | (incorrect) |
75 | cat hello > world < universe | |
76 | echo hello >$world | |
77 | ||
78 | (correct) | |
79 | cat hello >world <universe | |
80 | echo hello >"$world" | |
81 | ||
6d0618a8 JS |
82 | - We prefer $( ... ) for command substitution; unlike ``, it |
83 | properly nests. It should have been the way Bourne spelled | |
84 | it from day one, but unfortunately isn't. | |
85 | ||
860f70f9 TH |
86 | - If you want to find out if a command is available on the user's |
87 | $PATH, you should use 'type <command>', instead of 'which <command>'. | |
031fd4b9 | 88 | The output of 'which' is not machine parsable and its exit code |
860f70f9 TH |
89 | is not reliable across platforms. |
90 | ||
bc979945 JH |
91 | - We use POSIX compliant parameter substitutions and avoid bashisms; |
92 | namely: | |
6d0618a8 | 93 | |
bc979945 JH |
94 | - We use ${parameter-word} and its [-=?+] siblings, and their |
95 | colon'ed "unset or null" form. | |
6d0618a8 | 96 | |
bc979945 JH |
97 | - We use ${parameter#word} and its [#%] siblings, and their |
98 | doubled "longest matching" form. | |
6d0618a8 | 99 | |
bc979945 | 100 | - No "Substring Expansion" ${parameter:offset:length}. |
055467dd | 101 | |
bc979945 | 102 | - No shell arrays. |
6d0618a8 | 103 | |
bc979945 | 104 | - No pattern replacement ${parameter/pattern/string}. |
6d0618a8 | 105 | |
bc979945 JH |
106 | - We use Arithmetic Expansion $(( ... )). |
107 | ||
6d0618a8 JS |
108 | - We do not use Process Substitution <(list) or >(list). |
109 | ||
03b05c7d HV |
110 | - Do not write control structures on a single line with semicolon. |
111 | "then" should be on the next line for if statements, and "do" | |
112 | should be on the next line for "while" and "for". | |
113 | ||
9dbe7801 JH |
114 | (incorrect) |
115 | if test -f hello; then | |
116 | do this | |
117 | fi | |
118 | ||
119 | (correct) | |
120 | if test -f hello | |
121 | then | |
122 | do this | |
123 | fi | |
124 | ||
a378fee5 MD |
125 | - If a command sequence joined with && or || or | spans multiple |
126 | lines, put each command on a separate line and put && and || and | | |
127 | operators at the end of each line, rather than the start. This | |
128 | means you don't need to use \ to join lines, since the above | |
129 | operators imply the sequence isn't finished. | |
130 | ||
131 | (incorrect) | |
132 | grep blob verify_pack_result \ | |
133 | | awk -f print_1.awk \ | |
134 | | sort >actual && | |
135 | ... | |
136 | ||
137 | (correct) | |
138 | grep blob verify_pack_result | | |
139 | awk -f print_1.awk | | |
140 | sort >actual && | |
141 | ... | |
142 | ||
6d0618a8 JS |
143 | - We prefer "test" over "[ ... ]". |
144 | ||
145 | - We do not write the noiseword "function" in front of shell | |
146 | functions. | |
147 | ||
6117a3d4 JH |
148 | - We prefer a space between the function name and the parentheses, |
149 | and no space inside the parentheses. The opening "{" should also | |
150 | be on the same line. | |
151 | ||
152 | (incorrect) | |
153 | my_function(){ | |
154 | ... | |
155 | ||
156 | (correct) | |
157 | my_function () { | |
158 | ... | |
03b05c7d | 159 | |
009c98ee | 160 | - As to use of grep, stick to a subset of BRE (namely, no \{m,n\}, |
a58088ab | 161 | [::], [==], or [..]) for portability. |
009c98ee JH |
162 | |
163 | - We do not use \{m,n\}; | |
164 | ||
a58088ab | 165 | - We do not use ? or + (which are \{0,1\} and \{1,\} |
009c98ee JH |
166 | respectively in BRE) but that goes without saying as these |
167 | are ERE elements not BRE (note that \? and \+ are not even part | |
168 | of BRE -- making them accessible from BRE is a GNU extension). | |
169 | ||
5e9637c6 ÆAB |
170 | - Use Git's gettext wrappers in git-sh-i18n to make the user |
171 | interface translatable. See "Marking strings for translation" in | |
172 | po/README. | |
173 | ||
897f964c JH |
174 | - We do not write our "test" command with "-a" and "-o" and use "&&" |
175 | or "||" to concatenate multiple "test" commands instead, because | |
176 | the use of "-a/-o" is often error-prone. E.g. | |
177 | ||
178 | test -n "$x" -a "$a" = "$b" | |
179 | ||
180 | is buggy and breaks when $x is "=", but | |
181 | ||
182 | test -n "$x" && test "$a" = "$b" | |
183 | ||
184 | does not have such a problem. | |
185 | ||
a84fd3bc JH |
186 | - Even though "local" is not part of POSIX, we make heavy use of it |
187 | in our test suite. We do not use it in scripted Porcelains, and | |
188 | hopefully nobody starts using "local" before they are reimplemented | |
189 | in C ;-) | |
190 | ||
897f964c | 191 | |
6d0618a8 JS |
192 | For C programs: |
193 | ||
194 | - We use tabs to indent, and interpret tabs as taking up to | |
195 | 8 spaces. | |
196 | ||
197 | - We try to keep to at most 80 characters per line. | |
198 | ||
658df95a LS |
199 | - As a Git developer we assume you have a reasonably modern compiler |
200 | and we recommend you to enable the DEVELOPER makefile knob to | |
201 | ensure your patch is clear of all compiler warnings we care about, | |
202 | by e.g. "echo DEVELOPER=1 >>config.mak". | |
203 | ||
2de9b711 | 204 | - We try to support a wide range of C compilers to compile Git with, |
e88a2d02 ÆAB |
205 | including old ones. As of Git v2.35.0 Git requires C99 (we check |
206 | "__STDC_VERSION__"). You should not use features from a newer C | |
cc0c4297 | 207 | standard, even if your compiler groks them. |
a26fd033 | 208 | |
e88a2d02 ÆAB |
209 | New C99 features have been phased in gradually, if something's new |
210 | in C99 but not used yet don't assume that it's safe to use, some | |
211 | compilers we target have only partial support for it. These are | |
212 | considered safe to use: | |
cc0c4297 | 213 | |
442c27dd ÆAB |
214 | . since around 2007 with 2b6854c863a, we have been using |
215 | initializer elements which are not computable at load time. E.g.: | |
216 | ||
217 | const char *args[] = {"constant", variable, NULL}; | |
cc0c4297 JH |
218 | |
219 | . since early 2012 with e1327023ea, we have been using an enum | |
220 | definition whose last element is followed by a comma. This, like | |
221 | an array initializer that ends with a trailing comma, can be used | |
031fd4b9 | 222 | to reduce the patch noise when adding a new identifier at the end. |
cc0c4297 JH |
223 | |
224 | . since mid 2017 with cbc0f81d, we have been using designated | |
225 | initializers for struct (e.g. "struct t v = { .val = 'a' };"). | |
226 | ||
227 | . since mid 2017 with 512f41cf, we have been using designated | |
228 | initializers for array (e.g. "int array[10] = { [5] = 2 }"). | |
229 | ||
56a29d2c ÆAB |
230 | . since early 2021 with 765dc168882, we have been using variadic |
231 | macros, mostly for printf-like trace and debug macros. | |
232 | ||
82dd01d8 ÆAB |
233 | . since late 2021 with 44ba10d6, we have had variables declared in |
234 | the for loop "for (int i = 0; i < 10; i++)". | |
cc0c4297 | 235 | |
d7d850e2 ÆAB |
236 | New C99 features that we cannot use yet: |
237 | ||
238 | . %z and %zu as a printf() argument for a size_t (the %z being for | |
239 | the POSIX-specific ssize_t). Instead you should use | |
240 | printf("%"PRIuMAX, (uintmax_t)v). These days the MSVC version we | |
241 | rely on supports %z, but the C library used by MinGW does not. | |
242 | ||
438c2f85 ÆAB |
243 | . Shorthand like ".a.b = *c" in struct initializations is known to |
244 | trip up an older IBM XLC version, use ".a = { .b = *c }" instead. | |
245 | See the 33665d98 (reftable: make assignments portable to AIX xlc | |
246 | v12.01, 2022-03-28). | |
cc0c4297 JH |
247 | |
248 | - Variables have to be declared at the beginning of the block, before | |
249 | the first statement (i.e. -Wdeclaration-after-statement). | |
250 | ||
a26fd033 AS |
251 | - NULL pointers shall be written as NULL, not as 0. |
252 | ||
6d0618a8 JS |
253 | - When declaring pointers, the star sides with the variable |
254 | name, i.e. "char *string", not "char* string" or | |
255 | "char * string". This makes it easier to understand code | |
256 | like "char *string, c;". | |
257 | ||
f57b6cfd JK |
258 | - Use whitespace around operators and keywords, but not inside |
259 | parentheses and not around functions. So: | |
260 | ||
261 | while (condition) | |
262 | func(bar + 1); | |
263 | ||
264 | and not: | |
265 | ||
266 | while( condition ) | |
267 | func (bar+1); | |
268 | ||
5c7bb014 JH |
269 | - Do not explicitly compare an integral value with constant 0 or '\0', |
270 | or a pointer value with constant NULL. For instance, to validate that | |
271 | counted array <ptr, cnt> is initialized but has no elements, write: | |
272 | ||
273 | if (!ptr || cnt) | |
274 | BUG("empty array expected"); | |
275 | ||
276 | and not: | |
277 | ||
278 | if (ptr == NULL || cnt != 0); | |
279 | BUG("empty array expected"); | |
280 | ||
6d0618a8 JS |
281 | - We avoid using braces unnecessarily. I.e. |
282 | ||
283 | if (bla) { | |
284 | x = 1; | |
285 | } | |
286 | ||
1797dc51 JK |
287 | is frowned upon. But there are a few exceptions: |
288 | ||
289 | - When the statement extends over a few lines (e.g., a while loop | |
290 | with an embedded conditional, or a comment). E.g.: | |
291 | ||
292 | while (foo) { | |
293 | if (x) | |
294 | one(); | |
295 | else | |
296 | two(); | |
297 | } | |
298 | ||
299 | if (foo) { | |
300 | /* | |
301 | * This one requires some explanation, | |
302 | * so we're better off with braces to make | |
303 | * it obvious that the indentation is correct. | |
304 | */ | |
305 | doit(); | |
306 | } | |
307 | ||
308 | - When there are multiple arms to a conditional and some of them | |
309 | require braces, enclose even a single line block in braces for | |
310 | consistency. E.g.: | |
311 | ||
312 | if (foo) { | |
313 | doit(); | |
314 | } else { | |
315 | one(); | |
316 | two(); | |
317 | three(); | |
318 | } | |
6d0618a8 | 319 | |
691d0dd0 | 320 | - We try to avoid assignments in the condition of an "if" statement. |
0b0b8cd7 | 321 | |
6d0618a8 JS |
322 | - Try to make your code understandable. You may put comments |
323 | in, but comments invariably tend to stale out when the code | |
324 | they were describing changes. Often splitting a function | |
325 | into two makes the intention of the code much clearer. | |
326 | ||
b75a6ca7 | 327 | - Multi-line comments include their delimiters on separate lines from |
328 | the text. E.g. | |
329 | ||
330 | /* | |
331 | * A very long | |
332 | * multi-line comment. | |
333 | */ | |
334 | ||
cbcfd4e3 JH |
335 | Note however that a comment that explains a translatable string to |
336 | translators uses a convention of starting with a magic token | |
66f5f6dc | 337 | "TRANSLATORS: ", e.g. |
cbcfd4e3 | 338 | |
66f5f6dc ÆAB |
339 | /* |
340 | * TRANSLATORS: here is a comment that explains the string to | |
341 | * be translated, that follows immediately after it. | |
342 | */ | |
cbcfd4e3 JH |
343 | _("Here is a translatable string explained by the above."); |
344 | ||
6d0618a8 JS |
345 | - Double negation is often harder to understand than no negation |
346 | at all. | |
347 | ||
5db9ab82 JH |
348 | - There are two schools of thought when it comes to comparison, |
349 | especially inside a loop. Some people prefer to have the less stable | |
350 | value on the left hand side and the more stable value on the right hand | |
351 | side, e.g. if you have a loop that counts variable i down to the | |
352 | lower bound, | |
353 | ||
354 | while (i > lower_bound) { | |
355 | do something; | |
356 | i--; | |
357 | } | |
358 | ||
359 | Other people prefer to have the textual order of values match the | |
360 | actual order of values in their comparison, so that they can | |
361 | mentally draw a number line from left to right and place these | |
362 | values in order, i.e. | |
363 | ||
364 | while (lower_bound < i) { | |
365 | do something; | |
366 | i--; | |
367 | } | |
368 | ||
369 | Both are valid, and we use both. However, the more "stable" the | |
370 | stable side becomes, the more we tend to prefer the former | |
371 | (comparison with a constant, "i > 0", is an extreme example). | |
372 | Just do not mix styles in the same part of the code and mimic | |
373 | existing styles in the neighbourhood. | |
374 | ||
f26443da JH |
375 | - There are two schools of thought when it comes to splitting a long |
376 | logical line into multiple lines. Some people push the second and | |
377 | subsequent lines far enough to the right with tabs and align them: | |
378 | ||
379 | if (the_beginning_of_a_very_long_expression_that_has_to || | |
380 | span_more_than_a_single_line_of || | |
381 | the_source_text) { | |
382 | ... | |
383 | ||
384 | while other people prefer to align the second and the subsequent | |
385 | lines with the column immediately inside the opening parenthesis, | |
386 | with tabs and spaces, following our "tabstop is always a multiple | |
387 | of 8" convention: | |
388 | ||
389 | if (the_beginning_of_a_very_long_expression_that_has_to || | |
390 | span_more_than_a_single_line_of || | |
391 | the_source_text) { | |
392 | ... | |
393 | ||
394 | Both are valid, and we use both. Again, just do not mix styles in | |
395 | the same part of the code and mimic existing styles in the | |
396 | neighbourhood. | |
397 | ||
398 | - When splitting a long logical line, some people change line before | |
399 | a binary operator, so that the result looks like a parse tree when | |
400 | you turn your head 90-degrees counterclockwise: | |
401 | ||
402 | if (the_beginning_of_a_very_long_expression_that_has_to | |
403 | || span_more_than_a_single_line_of_the_source_text) { | |
404 | ||
405 | while other people prefer to leave the operator at the end of the | |
406 | line: | |
407 | ||
408 | if (the_beginning_of_a_very_long_expression_that_has_to || | |
409 | span_more_than_a_single_line_of_the_source_text) { | |
410 | ||
411 | Both are valid, but we tend to use the latter more, unless the | |
412 | expression gets fairly complex, in which case the former tends to | |
413 | be easier to read. Again, just do not mix styles in the same part | |
414 | of the code and mimic existing styles in the neighbourhood. | |
415 | ||
416 | - When splitting a long logical line, with everything else being | |
417 | equal, it is preferable to split after the operator at higher | |
418 | level in the parse tree. That is, this is more preferable: | |
419 | ||
420 | if (a_very_long_variable * that_is_used_in + | |
421 | a_very_long_expression) { | |
422 | ... | |
423 | ||
424 | than | |
425 | ||
426 | if (a_very_long_variable * | |
427 | that_is_used_in + a_very_long_expression) { | |
428 | ... | |
429 | ||
6d0618a8 JS |
430 | - Some clever tricks, like using the !! operator with arithmetic |
431 | constructs, can be extremely confusing to others. Avoid them, | |
432 | unless there is a compelling reason to use them. | |
433 | ||
434 | - Use the API. No, really. We have a strbuf (variable length | |
435 | string), several arrays with the ALLOC_GROW() macro, a | |
c455c87c | 436 | string_list for sorted string lists, a hash map (mapping struct |
6d0618a8 JS |
437 | objects) named "struct decorate", amongst other things. |
438 | ||
d9f079ad JH |
439 | - When you come up with an API, document its functions and structures |
440 | in the header file that exposes the API to its callers. Use what is | |
441 | in "strbuf.h" as a model for the appropriate tone and level of | |
442 | detail. | |
6d0618a8 | 443 | |
412cb2ec | 444 | - The first #include in C files, except in platform specific compat/ |
8bff5ca0 EN |
445 | implementations and sha1dc/, must be either "git-compat-util.h" or |
446 | one of the approved headers that includes it first for you. (The | |
447 | approved headers currently include "cache.h", "builtin.h", | |
448 | "t/helper/test-tool.h", "xdiff/xinclude.h", or | |
449 | "reftable/system.h"). You do not have to include more than one of | |
450 | these. | |
412cb2ec JH |
451 | |
452 | - A C file must directly include the header files that declare the | |
453 | functions and the types it uses, except for the functions and types | |
454 | that are made available to it by including one of the header files | |
455 | it must include by the previous rule. | |
6d0618a8 JS |
456 | |
457 | - If you are planning a new command, consider writing it in shell | |
458 | or perl first, so that changes in semantics can be easily | |
2de9b711 | 459 | changed and discussed. Many Git commands started out like |
6d0618a8 JS |
460 | that, and a few are still scripts. |
461 | ||
2de9b711 | 462 | - Avoid introducing a new dependency into Git. This means you |
6d0618a8 | 463 | usually should stay away from scripting languages not already |
2de9b711 | 464 | used in the Git core command set (unless your command is clearly |
6d0618a8 | 465 | separate from it, such as an importer to convert random-scm-X |
2de9b711 | 466 | repositories to Git). |
57199892 KB |
467 | |
468 | - When we pass <string, length> pair to functions, we should try to | |
469 | pass them in that order. | |
c455bd89 | 470 | |
5e9637c6 ÆAB |
471 | - Use Git's gettext wrappers to make the user interface |
472 | translatable. See "Marking strings for translation" in po/README. | |
473 | ||
89a9f2c8 JK |
474 | - Variables and functions local to a given source file should be marked |
475 | with "static". Variables that are visible to other source files | |
476 | must be declared with "extern" in header files. However, function | |
477 | declarations should not use "extern", as that is already the default. | |
478 | ||
f547101b ES |
479 | - You can launch gdb around your program using the shorthand GIT_DEBUGGER. |
480 | Run `GIT_DEBUGGER=1 ./bin-wrappers/git foo` to simply use gdb as is, or | |
481 | run `GIT_DEBUGGER="<debugger> <debugger-args>" ./bin-wrappers/git foo` to | |
482 | use your own debugger and arguments. Example: `GIT_DEBUGGER="ddd --gdb" | |
483 | ./bin-wrappers/git log` (See `wrap-for-bin.sh`.) | |
484 | ||
c5e366b1 TZ |
485 | For Perl programs: |
486 | ||
487 | - Most of the C guidelines above apply. | |
488 | ||
489 | - We try to support Perl 5.8 and later ("use Perl 5.008"). | |
490 | ||
491 | - use strict and use warnings are strongly preferred. | |
492 | ||
493 | - Don't overuse statement modifiers unless using them makes the | |
494 | result easier to follow. | |
495 | ||
496 | ... do something ... | |
497 | do_this() unless (condition); | |
498 | ... do something else ... | |
499 | ||
500 | is more readable than: | |
501 | ||
502 | ... do something ... | |
503 | unless (condition) { | |
504 | do_this(); | |
505 | } | |
506 | ... do something else ... | |
507 | ||
508 | *only* when the condition is so rare that do_this() will be almost | |
509 | always called. | |
510 | ||
511 | - We try to avoid assignments inside "if ()" conditions. | |
512 | ||
513 | - Learn and use Git.pm if you need that functionality. | |
514 | ||
9ef43dd7 JK |
515 | For Python scripts: |
516 | ||
517 | - We follow PEP-8 (http://www.python.org/dev/peps/pep-0008/). | |
518 | ||
45a87a83 | 519 | - As a minimum, we aim to be compatible with Python 2.7. |
9ef43dd7 JK |
520 | |
521 | - Where required libraries do not restrict us to Python 2, we try to | |
522 | also be compatible with Python 3.1 and later. | |
523 | ||
e258eb48 ES |
524 | |
525 | Program Output | |
526 | ||
527 | We make a distinction between a Git command's primary output and | |
528 | output which is merely chatty feedback (for instance, status | |
529 | messages, running transcript, or progress display), as well as error | |
530 | messages. Roughly speaking, a Git command's primary output is that | |
531 | which one might want to capture to a file or send down a pipe; its | |
532 | chatty output should not interfere with these use-cases. | |
533 | ||
534 | As such, primary output should be sent to the standard output stream | |
535 | (stdout), and chatty output should be sent to the standard error | |
536 | stream (stderr). Examples of commands which produce primary output | |
537 | include `git log`, `git show`, and `git branch --list` which generate | |
538 | output on the stdout stream. | |
539 | ||
540 | Not all Git commands have primary output; this is often true of | |
541 | commands whose main function is to perform an action. Some action | |
542 | commands are silent, whereas others are chatty. An example of a | |
543 | chatty action commands is `git clone` with its "Cloning into | |
544 | '<path>'..." and "Checking connectivity..." status messages which it | |
545 | sends to the stderr stream. | |
546 | ||
547 | Error messages from Git commands should always be sent to the stderr | |
548 | stream. | |
549 | ||
550 | ||
0ae0e882 PO |
551 | Error Messages |
552 | ||
553 | - Do not end error messages with a full stop. | |
554 | ||
151b6c2d JH |
555 | - Do not capitalize the first word, only because it is the first word |
556 | in the message ("unable to open %s", not "Unable to open %s"). But | |
557 | "SHA-3 not supported" is fine, because the reason the first word is | |
558 | capitalized is not because it is at the beginning of the sentence, | |
559 | but because the word would be spelled in capital letters even when | |
560 | it appeared in the middle of the sentence. | |
0ae0e882 PO |
561 | |
562 | - Say what the error is first ("cannot open %s", not "%s: cannot open") | |
563 | ||
564 | ||
35840a3e JH |
565 | Externally Visible Names |
566 | ||
567 | - For configuration variable names, follow the existing convention: | |
568 | ||
569 | . The section name indicates the affected subsystem. | |
570 | ||
571 | . The subsection name, if any, indicates which of an unbounded set | |
572 | of things to set the value for. | |
573 | ||
574 | . The variable name describes the effect of tweaking this knob. | |
575 | ||
576 | The section and variable names that consist of multiple words are | |
577 | formed by concatenating the words without punctuations (e.g. `-`), | |
578 | and are broken using bumpyCaps in documentation as a hint to the | |
579 | reader. | |
580 | ||
581 | When choosing the variable namespace, do not use variable name for | |
582 | specifying possibly unbounded set of things, most notably anything | |
583 | an end user can freely come up with (e.g. branch names). Instead, | |
584 | use subsection names or variable values, like the existing variable | |
585 | branch.<name>.description does. | |
586 | ||
587 | ||
c455bd89 ŠN |
588 | Writing Documentation: |
589 | ||
48bc1755 DW |
590 | Most (if not all) of the documentation pages are written in the |
591 | AsciiDoc format in *.txt files (e.g. Documentation/git.txt), and | |
592 | processed into HTML and manpages (e.g. git.html and git.1 in the | |
593 | same directory). | |
bb9f2aec | 594 | |
42e0fae9 MB |
595 | The documentation liberally mixes US and UK English (en_US/UK) |
596 | norms for spelling and grammar, which is somewhat unfortunate. | |
597 | In an ideal world, it would have been better if it consistently | |
598 | used only one and not the other, and we would have picked en_US | |
599 | (if you wish to correct the English of some of the existing | |
600 | documentation, please see the documentation-related advice in the | |
601 | Documentation/SubmittingPatches file). | |
602 | ||
5b1cd37e JH |
603 | In order to ensure the documentation is inclusive, avoid assuming |
604 | that an unspecified example person is male or female, and think | |
605 | twice before using "he", "him", "she", or "her". Here are some | |
606 | tips to avoid use of gendered pronouns: | |
607 | ||
608 | - Prefer succinctness and matter-of-factly describing functionality | |
609 | in the abstract. E.g. | |
610 | ||
611 | --short:: Emit output in the short-format. | |
612 | ||
613 | and avoid something like these overly verbose alternatives: | |
614 | ||
615 | --short:: Use this to emit output in the short-format. | |
616 | --short:: You can use this to get output in the short-format. | |
617 | --short:: A user who prefers shorter output could.... | |
618 | --short:: Should a person and/or program want shorter output, he | |
619 | she/they/it can... | |
620 | ||
621 | This practice often eliminates the need to involve human actors in | |
622 | your description, but it is a good practice regardless of the | |
623 | avoidance of gendered pronouns. | |
624 | ||
625 | - When it becomes awkward to stick to this style, prefer "you" when | |
c9dba103 | 626 | addressing the hypothetical user, and possibly "we" when |
5b1cd37e JH |
627 | discussing how the program might react to the user. E.g. |
628 | ||
629 | You can use this option instead of --xyz, but we might remove | |
630 | support for it in future versions. | |
631 | ||
632 | while keeping in mind that you can probably be less verbose, e.g. | |
633 | ||
634 | Use this instead of --xyz. This option might be removed in future | |
635 | versions. | |
636 | ||
637 | - If you still need to refer to an example person that is | |
638 | third-person singular, you may resort to "singular they" to avoid | |
639 | "he/she/him/her", e.g. | |
640 | ||
641 | A contributor asks their upstream to pull from them. | |
642 | ||
643 | Note that this sounds ungrammatical and unnatural to those who | |
644 | learned that "they" is only used for third-person plural, e.g. | |
645 | those who learn English as a second language in some parts of the | |
646 | world. | |
647 | ||
c455bd89 ŠN |
648 | Every user-visible change should be reflected in the documentation. |
649 | The same general rule as for code applies -- imitate the existing | |
ca03c368 JSJ |
650 | conventions. |
651 | ||
652 | A few commented examples follow to provide reference when writing or | |
653 | modifying command usage strings and synopsis sections in the manual | |
654 | pages: | |
c455bd89 | 655 | |
b1afe49d | 656 | Placeholders are spelled in lowercase and enclosed in angle brackets: |
c455bd89 ŠN |
657 | <file> |
658 | --sort=<key> | |
659 | --abbrev[=<n>] | |
660 | ||
9c9b4f2f AH |
661 | If a placeholder has multiple words, they are separated by dashes: |
662 | <new-branch-name> | |
663 | --template=<template-directory> | |
664 | ||
469bfc96 | 665 | Possibility of multiple occurrences is indicated by three dots: |
c455bd89 ŠN |
666 | <file>... |
667 | (One or more of <file>.) | |
668 | ||
669 | Optional parts are enclosed in square brackets: | |
6584fcc5 ÆAB |
670 | [<file>...] |
671 | (Zero or more of <file>.) | |
c455bd89 ŠN |
672 | |
673 | --exec-path[=<path>] | |
674 | (Option with an optional argument. Note that the "=" is inside the | |
675 | brackets.) | |
676 | ||
677 | [<patch>...] | |
678 | (Zero or more of <patch>. Note that the dots are inside, not | |
679 | outside the brackets.) | |
680 | ||
9c9b4f2f | 681 | Multiple alternatives are indicated with vertical bars: |
c455bd89 ŠN |
682 | [-q | --quiet] |
683 | [--utf8 | --no-utf8] | |
684 | ||
6584fcc5 ÆAB |
685 | Use spacing around "|" token(s), but not immediately after opening or |
686 | before closing a [] or () pair: | |
687 | Do: [-q | --quiet] | |
688 | Don't: [-q|--quiet] | |
689 | ||
548afb0d | 690 | Don't use spacing around "|" tokens when they're used to separate the |
6584fcc5 ÆAB |
691 | alternate arguments of an option: |
692 | Do: --track[=(direct|inherit)] | |
693 | Don't: --track[=(direct | inherit)] | |
694 | ||
c455bd89 | 695 | Parentheses are used for grouping: |
9c9b4f2f | 696 | [(<rev> | <range>)...] |
c455bd89 ŠN |
697 | (Any number of either <rev> or <range>. Parens are needed to make |
698 | it clear that "..." pertains to both <rev> and <range>.) | |
699 | ||
700 | [(-p <parent>)...] | |
701 | (Any number of option -p, each with one <parent> argument.) | |
702 | ||
703 | git remote set-head <name> (-a | -d | <branch>) | |
704 | (One and only one of "-a", "-d" or "<branch>" _must_ (no square | |
705 | brackets) be provided.) | |
706 | ||
707 | And a somewhat more contrived example: | |
708 | --diff-filter=[(A|C|D|M|R|T|U|X|B)...[*]] | |
709 | Here "=" is outside the brackets, because "--diff-filter=" is a | |
710 | valid usage. "*" has its own pair of brackets, because it can | |
711 | (optionally) be specified only when one or more of the letters is | |
712 | also provided. | |
48a8c26c TA |
713 | |
714 | A note on notation: | |
715 | Use 'git' (all lowercase) when talking about commands i.e. something | |
716 | the user would type into a shell and use 'Git' (uppercase first letter) | |
717 | when talking about the version control system and its properties. | |
ca03c368 JSJ |
718 | |
719 | A few commented examples follow to provide reference when writing or | |
720 | modifying paragraphs or option/command explanations that contain options | |
721 | or commands: | |
722 | ||
41f5b21f | 723 | Literal examples (e.g. use of command-line options, command names, |
0dbd305f CB |
724 | branch names, URLs, pathnames (files and directories), configuration and |
725 | environment variables) must be typeset in monospace (i.e. wrapped with | |
726 | backticks): | |
ca03c368 JSJ |
727 | `--pretty=oneline` |
728 | `git rev-list` | |
da0005b8 | 729 | `remote.pushDefault` |
0dbd305f CB |
730 | `http://git.example.com` |
731 | `.git/config` | |
41f5b21f | 732 | `GIT_DIR` |
57103dbf | 733 | `HEAD` |
41f5b21f TR |
734 | |
735 | An environment variable must be prefixed with "$" only when referring to its | |
736 | value and not when referring to the variable itself, in this case there is | |
737 | nothing to add except the backticks: | |
738 | `GIT_DIR` is specified | |
739 | `$GIT_DIR/hooks/pre-receive` | |
ca03c368 JSJ |
740 | |
741 | Word phrases enclosed in `backtick characters` are rendered literally | |
742 | and will not be further expanded. The use of `backticks` to achieve the | |
743 | previous rule means that literal examples should not use AsciiDoc | |
744 | escapes. | |
745 | Correct: | |
746 | `--pretty=oneline` | |
747 | Incorrect: | |
748 | `\--pretty=oneline` | |
749 | ||
750 | If some place in the documentation needs to typeset a command usage | |
751 | example with inline substitutions, it is fine to use +monospaced and | |
752 | inline substituted text+ instead of `monospaced literal text`, and with | |
753 | the former, the part that should not get substituted must be | |
754 | quoted/escaped. |