Re: [PATCH 0/3] preparatory patches for the submodule groups
- From
Stefan Beller <sbeller@google.com>
- Date
- May 3, 2016, 21:12 UTC
- Message-ID
- <CAGZ79kbm5y+LeyA_dwQWKFNaa42280cOvwQYZTP=-aRnySsB1A@mail.gmail.com>
- In-Reply-To
- <xmqqoa8mlutg.fsf@gitster.mtv.corp.google.com>
On Tue, May 3, 2016 at 2:01 PM, Junio C Hamano <gitster@pobox.com> wrote:
Show 18 quoted lines
> Stefan Beller <sbeller@google.com> writes: > >> I have your patch here and have a "-a and pathspec are incompatible" fix >> build on top. >> * I do wonder if we want to have the shortform '-a' though. > > I do not particularly care. I was merely matching the other two > options there. > >> * I think we want to head for consistency, eventually. >> e.g. commands with no arguments such as tag, branch >> give a list of their respective domain. > > Isn't that a historical mistake we are regretting, though? Only > after many other operation modes were invented and "create X" proves > not to be the only primary modes we had to invent "tag -l" and > "branch -l". Aren't we better off not having "no option means list" > kind of default?
listing is not destructive, and I really like to not type a single dash for some commands.
Show 9 quoted lines
> >> Subcommands do not give lists by default, e.g. >> `git stash clear`, `git remote prune` >> which are the moral equivalent to >> `git submodule deinit` just work as they were told, no --switch needed. > > I wouldn't say "git rm" should remove everything by extending that > logic, but I can certainly buy if somebody argues "git submodule > deinit" is not destructive enough to warrant extra safety.
`git rm` is a command, not a subcommand though.