git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Duy Nguyen <pclouds@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Stefan Beller <sbeller@google.com>,
	Jacob Keller <jacob.keller@gmail.com>,
	Graeme Geldenhuys <graemeg@gmail.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: Git's inconsistent command line options
Date: Mon, 31 Aug 2015 17:10:29 +0700	[thread overview]
Message-ID: <CACsJy8D3J6RhtPPtSvtWfOb8BapaX2-52M5_fE36psQPB_oQsQ@mail.gmail.com> (raw)
In-Reply-To: <xmqqa8tfvsr9.fsf@gitster.dls.corp.google.com>

On Wed, Aug 26, 2015 at 6:43 AM, Junio C Hamano <gitster@pobox.com> wrote:
> ...
>
> I do not see a good way to do such a safe transition with command
> words approach, *unless* we are going to introduce new commands,
> i.e. "git list-tag", "git create-tag", etc.

I'm probably shot down for this. But could we go with a clean plate
and create a new command prefix (something like git-next, git2, or
gt...)? We could then redesign the entire UI without worrying about
backward compatibility. At some point we can start to deprecate "git"
and encourage to use the new command prefix only. Of course somebody
has to go over all the commands and options to propose some consistent
UI, then more discussions and coding so it could likely follow the
path of pack v4..
-- 
Duy

  parent reply	other threads:[~2015-08-31 10:11 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
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 [this message]
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

  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=CACsJy8D3J6RhtPPtSvtWfOb8BapaX2-52M5_fE36psQPB_oQsQ@mail.gmail.com \
    --to=pclouds@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=graemeg@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. 
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).