Change mentions of "git programs" to "git commands"
Most of the docs and printouts refer to "commands" when discussing what the end users call via the "git" top-level program. We should refer them as "git programs" when we discuss the fact that the commands are implemented as separate programs, but in other contexts, it is better to use the term "git commands" consistently. Signed-off-by: Ori Avtalion <ori@avtalion.name> Signed-off-by: Nanako Shiraishi <nanako3@lavabit.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Ori Avtalion committed
Aug 7, 2009 at 17:24 UTC
57f6ec029090f64377ec5c0926b6e2e39b0caa4f
8 files changed
+10
-10
Documentation/config.txt
+2
-2
@@ -604,7 +604,7 @@ color.interactive.<slot>::
604
Use customized color for 'git-add --interactive'
605
output. `<slot>` may be `prompt`, `header`, `help` or `error`, for
606
four distinct types of normal output from interactive
607
- programs. The values of these variables may be specified as
607
+ commands. The values of these variables may be specified as
608
in color.branch.<slot>.
609
610
color.pager::
@@ -1100,7 +1100,7 @@ instaweb.port::
1100
linkgit:git-instaweb[1].
1101
1102
interactive.singlekey::
1103
- In interactive programs, allow the user to provide one-letter
1103
+ In interactive commands, allow the user to provide one-letter
1104
input with a single key (i.e., without hitting enter).
1105
Currently this is used only by the `\--patch` mode of
1106
linkgit:git-add[1]. Note that this setting is silently
Documentation/fetch-options.txt
+1
-1
@@ -1,7 +1,7 @@
1
-q::
2
--quiet::
3
Pass --quiet to git-fetch-pack and silence any other internally
4
- used programs.
4
+ used git commands.
5
6
-v::
7
--verbose::
Documentation/git-rev-list.txt
+1
-1
@@ -83,7 +83,7 @@ between the two operands. The following two commands are equivalent:
83
$ git rev-list A...B
84
-----------------------------------------------------------------------
85
86
-'git-rev-list' is a very essential git program, since it
86
+'rev-list' is a very essential git command, since it
87
provides the ability to build and traverse commit ancestry graphs. For
88
this reason, it has a lot of different options that enables it to be
89
used by commands as different as 'git-bisect' and
Documentation/git.txt
+1
-1
@@ -315,7 +315,7 @@ Synching repositories
315
316
include::cmds-synchingrepositories.txt[]
317
318
-The following are helper programs used by the above; end users
318
+The following are helper commands used by the above; end users
319
typically do not use them directly.
320
321
include::cmds-synchelpers.txt[]
Documentation/gitattributes.txt
+1
-1
@@ -404,7 +404,7 @@ Performing a three-way merge
404
405
The attribute `merge` affects how three versions of a file is
406
merged when a file-level merge is necessary during `git merge`,
407
-and other programs such as `git revert` and `git cherry-pick`.
407
+and other commands such as `git revert` and `git cherry-pick`.
408
409
Set::
410
Documentation/gitcore-tutorial.txt
+2
-2
@@ -12,7 +12,7 @@ git *
12
DESCRIPTION
13
-----------
14
15
-This tutorial explains how to use the "core" git programs to set up and
15
+This tutorial explains how to use the "core" git commands to set up and
16
work with a git repository.
17
18
If you just need to use git as a revision control system you may prefer
@@ -1328,7 +1328,7 @@ into it later. Obviously, this repository creation needs to be
1328
done only once.
1329
1330
[NOTE]
1331
-'git-push' uses a pair of programs,
1331
+'git-push' uses a pair of commands,
1332
'git-send-pack' on your local machine, and 'git-receive-pack'
1333
on the remote machine. The communication between the two over
1334
the network internally uses an SSH connection.
Documentation/user-manual.txt
+1
-1
@@ -4131,7 +4131,7 @@ What does this mean?
4131
4132
`git rev-list` is the original version of the revision walker, which
4133
_always_ printed a list of revisions to stdout. It is still functional,
4134
-and needs to, since most new Git programs start out as scripts using
4134
+and needs to, since most new Git commands start out as scripts using
4135
`git rev-list`.
4136
4137
`git rev-parse` is not as important any more; it was only used to filter out
help.c
+1
-1
@@ -334,7 +334,7 @@ const char *help_unknown_cmd(const char *cmd)
334
const char *assumed = main_cmds.names[0]->name;
335
main_cmds.names[0] = NULL;
336
clean_cmdnames(&main_cmds);
337
- fprintf(stderr, "WARNING: You called a Git program named '%s', "
337
+ fprintf(stderr, "WARNING: You called a Git command named '%s', "
338
"which does not exist.\n"
339
"Continuing under the assumption that you meant '%s'\n",
340
cmd, assumed);