git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "mana vortex" <manavortex@gmail.com>
To: git@vger.kernel.org
Subject: [bug-ish] [convenience] fatal: only [12] (reference)s? expected, [12] given
Date: Wed, 30 May 2018 10:12:41 +0200	[thread overview]
Message-ID: <1B7D3974-AA1C-42B5-A7F5-C5A36B28C34F@gmail.com> (raw)

Hello git folks,
I’m writing about something that annoys me since forever: The 
reference handling is not consistent between commands. For example, I do

git checkout origin master

but I do

git reset —hard origin/master

I always get it wrong the first time.

Is there a convenience option that circumvents the error?

If one argument is given, but two are expected, split the argument at 
the first / and retry - throw error if that isn’t valid
If two arguments are given, but one is expected, concat the arguments 
with a /.

Is that possible already, and if not, would you care to implement it?

Thank you for your time.

             reply	other threads:[~2018-05-30  8:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-30  8:12 mana vortex [this message]
2018-05-30 18:11 ` [bug-ish] [convenience] fatal: only [12] (reference)s? expected, [12] given Stefan Beller

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=1B7D3974-AA1C-42B5-A7F5-C5A36B28C34F@gmail.com \
    --to=manavortex@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).