From: Denton Liu <liu.denton@gmail.com>
To: git@vger.kernel.org
Cc: pclouds@gmail.com
Subject: [PATCH v2 1/3] git-remote.txt: be specific about default behavior
Date: Tue, 12 Feb 2019 01:56:09 -0800 [thread overview]
Message-ID: <7e7e0dde0495e105bb717418745cc24edd051887.1549965172.git.liu.denton@gmail.com> (raw)
In-Reply-To: <cover.1549965172.git.liu.denton@gmail.com>
Instead of beating around the bush, we directly specify the subcommand
that is called by default when none are provided. This way, a user will
know where to look for more information.
---
Documentation/git-remote.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/git-remote.txt b/Documentation/git-remote.txt
index 0cad37fb81..a2e685818b 100644
--- a/Documentation/git-remote.txt
+++ b/Documentation/git-remote.txt
@@ -41,8 +41,8 @@ OPTIONS
COMMANDS
--------
-With no arguments, shows a list of existing remotes. Several
-subcommands are available to perform operations on the remotes.
+With no arguments, the default command is 'show'. Several subcommands are
+available to perform operations on the remotes.
'add'::
--
2.20.1.522.gd8785cdd01
next prev parent reply other threads:[~2019-02-12 9:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 4:03 [PATCH] git-submodule.txt: document default behavior Denton Liu
2019-02-12 5:33 ` Duy Nguyen
2019-02-12 9:56 ` [PATCH v2 0/3] Document git-submodule's " Denton Liu
2019-02-12 9:56 ` Denton Liu [this message]
2019-02-12 9:56 ` [PATCH v2 2/3] git-submodule.txt: make subcommands underlined Denton Liu
2019-02-13 8:15 ` Denton Liu
2019-02-13 9:55 ` Duy Nguyen
2019-02-13 18:30 ` Junio C Hamano
2019-02-12 9:56 ` [PATCH v2 3/3] submodule: document default behavior Denton Liu
2019-02-13 18:39 ` Junio C Hamano
2019-02-14 7:24 ` Denton Liu
2019-02-14 17:41 ` Junio C Hamano
2019-02-15 9:26 ` [PATCH v3 0/1] Document git-submodule's " Denton Liu
2019-02-15 9:26 ` [PATCH v3 1/1] submodule: document " Denton Liu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7e7e0dde0495e105bb717418745cc24edd051887.1549965172.git.liu.denton@gmail.com \
--to=liu.denton@gmail.com \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).