git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Graeme Geldenhuys" <graemeg@gmail.com>
To: git@vger.kernel.org
Subject: Git's inconsistent command line options
Date: Tue, 25 Aug 2015 08:01:24 +0000 (UTC)	[thread overview]
Message-ID: <mrh7ck$r0g$1@ger.gmane.org> (raw)

Hi,

I've used Git for years and this has always bothered me. Has anybody
else noticed the inconsistent command line parameteres for seemingly
similar tasks. There are many examples, but I'll list only two (I can
supply a more extensive list if needed).

eg: Renaming things.

 * When working with branches it uses "-m" or "-M" to rename a branch.

 * When working with remote repos it use "rename"  (not even the more
common -- prefix either).

eg: Deleting things

  * When working with branches it uses "-d" or "-D" to delete a branch

  * When working with remote branch it uses only a push command.

  * When deleting a remote repo it uses "remove" (again not even with
the commonly used -- prefix)


Even though I have worked with Git since 2009, I still have to
reference the help to remind me of what parameter to use in certain
situation simply because similar tasks differ so much.

Maybe we could address this in the next major version of Git? Has
anybody else thought about this or started work on this? Or was this
discussed before and declined (link?).

Regards,
  Graeme

             reply	other threads:[~2015-08-25  8:05 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-25  8:01 Graeme Geldenhuys [this message]
2015-08-25 15:13 ` Git's inconsistent command line options 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
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='mrh7ck$r0g$1@ger.gmane.org' \
    --to=graemeg@gmail.com \
    --cc=git@vger.kernel.org \
    /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).