diff options
| author | Kristoffer Haugsbakk <code@khaugsbakk.name> | 2024-03-01 18:05:53 (GMT) |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2024-03-01 18:45:01 (GMT) |
| commit | 7a96b75e05953d377b42b01e171f884357772611 (patch) | |
| tree | a4220a06fc401057beab343fb4c62d98f11cc8a9 /Documentation | |
| parent | 0f9d4d28b7e6021b7e6db192b7bf47bd3a0d0d1d (diff) | |
| download | git-7a96b75e05953d377b42b01e171f884357772611.zip git-7a96b75e05953d377b42b01e171f884357772611.tar.gz git-7a96b75e05953d377b42b01e171f884357772611.tar.bz2 | |
gitcli: drop mention of “non-dashed form”
Git builtins used to be called like e.g. `git-commit`, not `git
commit` (*dashed form* and *non-dashed form*, respectively). The dashed
form was deprecated in version 1.5.4 (2006). Now only a few commands
have an alternative dashed form when `SKIP_DASHED_BUILT_INS` is
active.[1]
The mention here is from 2f7ee089dff (parse-options: Add a gitcli(5) man
page., 2007-12-13), back when the deprecation was relatively
recent. These days though it seems like an irrelevant point to make to
budding CLI scripters—you don’t have to warn against a style that
probably doesn’t even work on their git(1) installation.
† 1: 179227d6e21 (Optionally skip linking/copying the built-ins,
2020-09-21)
Signed-off-by: Kristoffer Haugsbakk <code@khaugsbakk.name>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation')
| -rw-r--r-- | Documentation/gitcli.txt | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/Documentation/gitcli.txt b/Documentation/gitcli.txt index e5fac94..7c70932 100644 --- a/Documentation/gitcli.txt +++ b/Documentation/gitcli.txt @@ -81,9 +81,6 @@ you will. Here are the rules regarding the "flags" that you should follow when you are scripting Git: - * It's preferred to use the non-dashed form of Git commands, which means that - you should prefer `git foo` to `git-foo`. - * Splitting short options to separate words (prefer `git foo -a -b` to `git foo -ab`, the latter may not even work). |