From: Junio C Hamano <gitster@pobox.com>
To: Nicholas Guriev <guriev-ns@ya.ru>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] worktree: treat "list" as default command
Date: Sat, 13 Jun 2020 09:36:16 -0700 [thread overview]
Message-ID: <xmqqr1uizzwf.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <202006130730.05D7UB99010559@dandelion.mymedia.su> (Nicholas Guriev's message of "Sat, 13 Jun 2020 10:14:21 +0300")
Nicholas Guriev <guriev-ns@ya.ru> writes:
> Perceive simple "git worktree" without a subcommand as "git worktree list"
> for consistency with "git submodule" that already can work in such a way.
"git branch" works the same way, and probably "git remote", too?
"git config" doesn't work that way, though. Should it default to
the list mode (rhetorical/tongue-in-cheek question---but it gives a
hint for writing the justification to decide where to draw the line).
next prev parent reply other threads:[~2020-06-13 16:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-13 7:14 [PATCH] worktree: treat "list" as default command Nicholas Guriev
2020-06-13 16:36 ` Junio C Hamano [this message]
2020-06-14 5:56 ` Eric Sunshine
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqr1uizzwf.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=guriev-ns@ya.ru \
/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.
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 NNTP newsgroup(s).