git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luciano Miguel Ferreira Rocha <luciano@eurotux.com>
To: Andreas Ericsson <ae@op5.se>
Cc: Ondrej Certik <ondrej@certik.cz>, Git Mailing List <git@vger.kernel.org>
Subject: Re: default aliases (ci, di, st, co)
Date: Thu, 9 Jul 2009 09:58:37 +0100	[thread overview]
Message-ID: <20090709085837.GA12348@bit.office.eurotux.com> (raw)
In-Reply-To: <4A55958E.1050401@op5.se>

[-- Attachment #1: Type: text/plain, Size: 1469 bytes --]

On Thu, Jul 09, 2009 at 09:00:30AM +0200, Andreas Ericsson wrote:
>  Ondrej Certik wrote:
> > Hi,
> > coming to git from mercurial and svn, here is the alias part of my 
> > .gitconfig:
> > [alias]
> >     ci = commit
> >     di = diff --color-words
> >     st = status
> >     co = checkout
> > And all is fine until I share commands to checkout my branch (for
> > example) with other people, then basically I have to write those
> > commands in full (e.g. commit, checkout, ...), since I cannot assume
> > they have their .gitconfig setup the same way I do. Especially for
> > people who are new to git.
> > What is the view on this in the git community?
> 
> 
>  Personally I think "plain" aliases like you use above are evil.
>  git is not svn or mercurial. If you use it like svn you'll be
>  surprised sooner or later and your workflow will feel awkward or
>  just plain wrong. hg and git are very similar, but the fact that
>  hg assumed the svn shorthands implies to me that they've tried
>  to retain a compatibility that does not, in fact, exist.

No, it just means that shorting common commands is useful and common.

>  I have no simple aliases for any of the commands. There's just no reason
>  for them since tab completion works so well.

"Intelligent" bash completion always gets in my way, so I can't use it.

I vote yes.

-- 
Luciano Rocha <luciano@eurotux.com>
Eurotux Informática, S.A. <http://www.eurotux.com/>

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

  parent reply	other threads:[~2009-07-09  8:58 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-08 23:49 default aliases (ci, di, st, co) Ondrej Certik
2009-07-09  0:13 ` Jakub Narebski
2009-07-09  8:58   ` Graeme Geldenhuys
2009-07-09 16:43   ` Junio C Hamano
2009-07-09 23:08     ` Paolo Bonzini
2009-07-13  6:40       ` Jeff King
2009-07-13  6:43         ` Jeff King
2009-07-13  9:15         ` Paolo Bonzini
2009-07-09  7:00 ` Andreas Ericsson
2009-07-09  8:50   ` Michael J Gruber
2009-07-09  9:04     ` Graeme Geldenhuys
2009-07-09  9:40     ` Jakub Narebski
2009-07-09  9:48       ` Michael J Gruber
2009-07-09  8:58   ` Luciano Miguel Ferreira Rocha [this message]
2009-07-12  5:07     ` Ondrej Certik
     [not found]   ` <20090709160249.GA12830@cthulhu>
2009-07-09 20:54     ` wsfix alias Andreas Ericsson
2009-07-09 21:30       ` Larry D'Anna
2009-07-09  9:01 ` default aliases (ci, di, st, co) Graeme Geldenhuys
2009-07-09  9:12   ` Matthieu Moy

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=20090709085837.GA12348@bit.office.eurotux.com \
    --to=luciano@eurotux.com \
    --cc=ae@op5.se \
    --cc=git@vger.kernel.org \
    --cc=ondrej@certik.cz \
    /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).