From: Andreas Ericsson <ae@op5.se>
To: Git List <git@vger.kernel.org>
Subject: git shorthands (was: Re: Wine + GIT)
Date: Tue, 06 Dec 2005 22:22:27 +0100 [thread overview]
Message-ID: <43960113.8000209@op5.se> (raw)
In-Reply-To: <1133891589.8577.63.camel@cashmere.sps.mot.com>
Jon Loeliger wrote:
>
> That way:
> "git mer" would fail
> "git merge" would run "git-merge"
> "git merge-" would fail
> "git merge-o" would fail,
> "git-merge-oc" would run "git-merge-octopus".
>
> Any interest? Overkill? Bad idea?
>
I think it's overkill. It would be better, methinks, to add mnemonic-ish
shorthands for the porcelainish commands, so that
git fp => git-format-patch
git co => git-checkout
git up => git-update-index
git octo => git-merge-octopus
git fsck => git-fsck-objects
git hash => git-hash-object
and so on...
This because non-ambiguous is rarely logical (for git at least, which
has 'git-<family>-<action | object-type>) unless one knows the entire
command anyways. Ambiguity may also be introduced by later commands, and
then you'll need to re-learn them. I always find that annoying.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2005-12-06 21:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-05 23:29 Wine + GIT Mike McCormack
2005-12-06 2:03 ` Jeff Garzik
2005-12-06 2:26 ` Junio C Hamano
2005-12-06 17:08 ` J. Bruce Fields
2005-12-06 17:33 ` Junio C Hamano
2005-12-06 17:39 ` J. Bruce Fields
2005-12-06 17:53 ` Jon Loeliger
2005-12-06 21:22 ` Andreas Ericsson [this message]
2005-12-07 0:56 ` Ben Clifford
2005-12-06 19:01 ` Jeff Garzik
2005-12-06 19:06 ` Mike McCormack
2005-12-06 2:18 ` Jeff Garzik
2005-12-06 23:08 ` Nick Hengeveld
2005-12-06 23:27 ` Andreas Ericsson
2005-12-06 9:02 ` Marco Costalba
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=43960113.8000209@op5.se \
--to=ae@op5.se \
--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).