git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael G Schwern <schwern@pobox.com>
To: git@vger.kernel.org
Subject: git silently ignores aliases of existing commands
Date: Fri, 17 Jul 2009 17:52:49 -0700	[thread overview]
Message-ID: <4A611CE1.3080709@pobox.com> (raw)

Everyone says "git tag" does the wrong thing by default and what you really
want is an annotated tag with "git tag -a".  So I figured I'd fix the default
and in my .gitconfig added:

[alias]
    tag = tag -a

and considered it done.  Weeks later I discovered git was ignoring that alias
and I was still making lightweight tags.

It would be nice if git used the alias *before* the installed command.  This
lets me fix/change default behaviors without having to come up with a new
command.  (Another handy example:  blame = blame -w)  It doesn't do anything
useful right now anyway.

Whether or not that changes, if an alias is being ignored git should warn me.
 This informs the user their perfectly sensible action has not done what they
expected.  In addition, should git add a command in the future which conflicts
with the name of an alias they'll know.


PS  I couldn't find anything obvious about where to send bug reports / feature
requests in the git man page, just "general upbringing" pointing here.  It
would be helpful if it was a bit more clear.  None of "bug", "report" or
"issue" pointed at anything relevant.

-- 
184. When operating a military vehicle I may *not* attempt something
     "I saw in a cartoon".
    -- The 213 Things Skippy Is No Longer Allowed To Do In The U.S. Army
           http://skippyslist.com/list/

             reply	other threads:[~2009-07-18  1:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-18  0:52 Michael G Schwern [this message]
2009-07-18  2:01 ` git silently ignores aliases of existing commands Sean Estabrooks
2009-07-18  7:16   ` Michael G Schwern
2009-07-18  9:30     ` demerphq
2009-07-18 10:46       ` Jeff King
2009-07-18 10:55         ` demerphq
2009-07-18 10:58           ` Jeff King
2009-07-18 11:20             ` demerphq
2009-07-18 16:12               ` A Large Angry SCM

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=4A611CE1.3080709@pobox.com \
    --to=schwern@pobox.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).