From: Junio C Hamano <gitster@pobox.com>
To: Duy Nguyen <pclouds@gmail.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
Git Mailing List <git@vger.kernel.org>, Jeff King <peff@peff.net>
Subject: Re: [PATCH/RFC] commit: add short option for --amend
Date: Fri, 17 Aug 2018 08:31:32 -0700 [thread overview]
Message-ID: <xmqqa7plc8mj.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <CACsJy8Di4GQLqkBmcnrfmU9aS=wizxU36Ly0BRgDEDmFG=+2Fg@mail.gmail.com> (Duy Nguyen's message of "Fri, 17 Aug 2018 16:33:30 +0200")
Duy Nguyen <pclouds@gmail.com> writes:
> The alternative is -A or -M which may be easier associated with
> --amend.
I would be confused to mistake that "git commit -A $args" would do
something similar to "git add -A && git commit $args".
I do my fair share of amends during the day, and I've never felt the
need for a short-hand, but perhaps that is just me. I am wondering
if "-E" (stands for 'edit', not 'A or M are out, and the next letter
in amend is E') is understandable and memorable enough---after all,
it is "editing" an existing commit, and the edit is done in a big
and different way than the existing "commit --edit".
But perhaps that reasoning is a bit too cute. I dunno.
next prev parent reply other threads:[~2018-08-17 15:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-16 18:31 [PATCH/RFC] commit: add short option for --amend Nguyễn Thái Ngọc Duy
2018-08-16 18:39 ` Jeff King
2018-08-16 18:46 ` Duy Nguyen
2018-08-17 6:47 ` Jonathan Nieder
2018-08-17 14:33 ` Duy Nguyen
2018-08-17 15:26 ` Jeff King
2018-08-17 15:31 ` Duy Nguyen
2018-08-17 15:31 ` Junio C Hamano [this message]
2018-08-18 7:24 ` Simon Ruderich
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=xmqqa7plc8mj.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
/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).