author | Ori Avtalion <ori@avtalion.name> | |
Fri, 7 Aug 2009 14:24:21 +0000 (17:24 +0300) | ||
committer | Junio C Hamano <gitster@pobox.com> | |
Wed, 12 Aug 2009 23:14:41 +0000 (16:14 -0700) | ||
commit | 57f6ec029090f64377ec5c0926b6e2e39b0caa4f | |
tree | 75e2db8a3d86ab3a5563dac423d044813a4341ef | tree | snapshot |
parent | 22f1fb66be859fb5ab1620a7dce8e54702d4a07c | commit | diff |
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>
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>