From: "Jörg Sommer" <joerg@alea.gnuu.de>
To: git@vger.kernel.org
Subject: Re: [PATCH] Check for -amend as a common wrong usage of --amend.
Date: Sat, 26 Jan 2008 00:10:21 +0000 (UTC) [thread overview]
Message-ID: <slrnfpkujd.all.joerg@alea.gnuu.de> (raw)
In-Reply-To: 4798D5E7.8070907@obry.net
Hi Pascal,
Pascal Obry <pascal@obry.net> wrote:
> Typing too fast I've just made this mistake the third time today. It is
> of course easy to revert but a check seems appropriate here.
Why not use an alias?
% git config --get alias.cia
commit --amend
Bye, Jörg.
--
Two types have compatible type if their types are the same.
[ANSI C, 6.2.7]
next prev parent reply other threads:[~2008-01-26 10:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-24 18:13 [PATCH] Check for -amend as a common wrong usage of --amend Pascal Obry
2008-01-24 18:16 ` Pascal Obry
2008-01-26 0:10 ` Jörg Sommer [this message]
2008-01-24 18:20 ` Johannes Schindelin
2008-01-24 18:52 ` Pascal Obry
2008-01-24 19:25 ` Charles Bailey
2008-01-24 19:35 ` Pascal Obry
2008-01-24 20:47 ` Joey Hess
2008-01-26 6:20 ` Junio C Hamano
2008-01-26 10:42 ` Pierre Habouzit
2008-01-26 11:26 ` [PATCH] parse-options: catch some likely in presense of aggregated options Pierre Habouzit
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=slrnfpkujd.all.joerg@alea.gnuu.de \
--to=joerg@alea.gnuu.de \
--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).