All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jacob Keller <jacob.keller@gmail.com>
Cc: Hilco Wijbenga <hilco.wijbenga@gmail.com>,
	Stefan Beller <sbeller@google.com>,
	Graeme Geldenhuys <graemeg@gmail.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: Git's inconsistent command line options
Date: Wed, 26 Aug 2015 13:48:54 -0700	[thread overview]
Message-ID: <xmqq1tep3he1.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CA+P7+xoV=NZvcUyqbdOpjcD1ykrpU7zrWB4JDVMSdBVC7EHEgw@mail.gmail.com> (Jacob Keller's message of "Wed, 26 Aug 2015 11:10:42 -0700")

Jacob Keller <jacob.keller@gmail.com> writes:

> On Wed, Aug 26, 2015 at 10:56 AM, Junio C Hamano <gitster@pobox.com> wrote:
>> But notice that I said "if you really want to".  I personally think
>> it is a road to madness.
>
> Agreed. I don't believe in command line API here. I think we'd need a
> better solution.
>
> My gut says: Live with the warts on old commands and try to make
> people use command words for new commands.

A transition to make everybody to use subsubcommands (thereby
changing what "git tag delete master" means) is impossible in
practice.  On the other hand, a transition to make everybody use
command mode options (thereby allowing "git worktree list" to be
also spelled as "git worktree --list") _is_ possible.

Has anybody created a handy catalog of Git commands with subcommands
and command mode options?  If we see such a list and replace the
column of subcommands with command mode options, we might find that
such a "command mode option only" world a pleasant future for us to
live in, or an unpleasant one that we have to keep typing two extra
dashes all the time.  I cannot tell offhand.

  reply	other threads:[~2015-08-26 20:49 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-25  8:01 Git's inconsistent command line options Graeme Geldenhuys
2015-08-25 15:13 ` Junio C Hamano
2015-08-25 21:49   ` Jacob Keller
2015-08-25 22:06     ` Stefan Beller
2015-08-25 22:21       ` Jacob Keller
2015-08-25 23:43       ` Junio C Hamano
2015-08-26  1:30         ` Hilco Wijbenga
2015-08-26 17:56           ` Junio C Hamano
2015-08-26 18:10             ` Jacob Keller
2015-08-26 20:48               ` Junio C Hamano [this message]
2015-08-26 22:52               ` Philip Oakley
2015-08-26 23:02                 ` Jacob Keller
2015-08-26 23:03                   ` Jacob Keller
2015-08-26  4:09         ` Jacob Keller
2015-08-26  6:28           ` Andreas Schwab
2015-08-26  6:33             ` Jacob Keller
2015-08-31 10:10         ` Duy Nguyen
2015-08-31 14:25           ` Barry Warsaw
2015-09-01  9:28             ` David Aguilar
2015-09-01 14:19               ` Barry Warsaw
2015-09-01 16:42                 ` Junio C Hamano
2015-09-01 17:50                   ` Barry Warsaw
2015-09-01 17:56                     ` Stefan Beller
2015-09-09  9:42                       ` Michael J Gruber
2015-09-09  9:42               ` Michael J Gruber

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=xmqq1tep3he1.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=graemeg@gmail.com \
    --cc=hilco.wijbenga@gmail.com \
    --cc=jacob.keller@gmail.com \
    --cc=sbeller@google.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.