diff options
author | Ori Avtalion <ori@avtalion.name> | 2009-08-07 17:24:21 +0300 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2009-08-12 16:14:41 -0700 |
commit | 57f6ec029090f64377ec5c0926b6e2e39b0caa4f (patch) | |
tree | 75e2db8a3d86ab3a5563dac423d044813a4341ef /help.c | |
parent | 22f1fb66be859fb5ab1620a7dce8e54702d4a07c (diff) | |
download | git-57f6ec029090f64377ec5c0926b6e2e39b0caa4f.tar.gz |
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>
Diffstat (limited to 'help.c')
-rw-r--r-- | help.c | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -334,7 +334,7 @@ const char *help_unknown_cmd(const char *cmd) const char *assumed = main_cmds.names[0]->name; main_cmds.names[0] = NULL; clean_cmdnames(&main_cmds); - fprintf(stderr, "WARNING: You called a Git program named '%s', " + fprintf(stderr, "WARNING: You called a Git command named '%s', " "which does not exist.\n" "Continuing under the assumption that you meant '%s'\n", cmd, assumed); |