From 7a96b75e05953d377b42b01e171f884357772611 Mon Sep 17 00:00:00 2001 From: Kristoffer Haugsbakk Date: Fri, 1 Mar 2024 19:05:53 +0100 Subject: =?UTF-8?q?gitcli:=20drop=20mention=20of=20=E2=80=9Cnon-dashed=20f?= =?UTF-8?q?orm=E2=80=9D?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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 Signed-off-by: Junio C Hamano 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). -- cgit v0.10.2-6-g49f6