From: Junio C Hamano <gitster@pobox.com>
To: Phil Hord <phil.hord@gmail.com>
Cc: "Romain Vimont (®om)" <rom@rom1v.com>, git@vger.kernel.org
Subject: Re: git commit --amen
Date: Thu, 04 Oct 2012 09:52:17 -0700 [thread overview]
Message-ID: <7va9w218ou.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CABURp0rbNZSOC_Jtxfjp+j3SQR=+r0pU6vOXvc0Jnth0UU9mDA@mail.gmail.com> (Phil Hord's message of "Thu, 4 Oct 2012 10:25:50 -0400")
Phil Hord <phil.hord@gmail.com> writes:
>> Is it normal that "git commit --amen" actually works ?
>> (it does like --amend)
>>
>> version 1.7.10.4
>
> Yes. From Documentation/technical/api-parse-options.txt:
>
> * Long options may be 'abbreviated', as long as the abbreviation
> is unambiguous.
>
> Apparently since 2008-06-22.
Notice "technical/api-" part; that is a _wrong_ documentation page
to quote to end users.
Instead quote from "git help cli".
From the git 1.5.4 series and further, many git commands (not
all of them at the time of the writing though) come with an
enhanced option parser.
> So 'git commit --am' also works. But it should probably be avoided
> because of its similarity to 'git commit -am'.
Yes, in general, you should avoid relying on shortened form
working. Git 2.4 may add an option "--amen" that has totally
different meaning.
next prev parent reply other threads:[~2012-10-04 22:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-04 14:10 git commit --amen Romain Vimont (®om)
2012-10-04 14:25 ` Phil Hord
2012-10-04 14:38 ` Romain Vimont (®om)
2012-10-04 14:57 ` Erik Faye-Lund
2012-10-04 16:52 ` Junio C Hamano
2012-10-04 16:52 ` Junio C Hamano [this message]
2012-10-04 17:13 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7va9w218ou.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=phil.hord@gmail.com \
--cc=rom@rom1v.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).