From: Michael Witten <mfwitten@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Olivier Goffart <ogoffart@kde.org>, git@vger.kernel.org
Subject: Re: Ability to edit message from git rebase --interactive.
Date: Fri, 10 Apr 2009 13:50:07 -0500 [thread overview]
Message-ID: <b4087cc50904101150i31f1bbfdre73bec44dac580eb@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0904102019250.10279@pacific.mpi-cbg.de>
On Fri, Apr 10, 2009 at 13:21, Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:
>>> I still think this feature to edit the message in git rebase -i is really
>>> usefull. =A0So 'm' is really taken, what about 'r' for 'rephrase'?
>>>
>>> or maybe 'rephrase' is something different?
>>
>> How about 'a' for an immediate [a]mend?
>
> git commit --amend lets you amend the modifications in addition to the
> message, so I think it would be too ambiguous.
How about edit-message|edit-m|em ?
Also, I still like the idea of being able to write:
git commit --amend HEAD~5 HEAD^
and then have the rebase setup and started for me.
How about:
git commit --amend-message ...
for just the commit message?
P.S.
Sorry for the duplicate, Johannes.
next prev parent reply other threads:[~2009-04-10 18:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-17 18:53 Ability to edit message from git rebase --interactive Olivier Goffart
2009-03-17 22:31 ` Johannes Schindelin
2009-03-18 0:40 ` Jeff King
2009-03-18 0:58 ` Johannes Schindelin
2009-03-18 1:06 ` Junio C Hamano
2009-03-18 5:42 ` Sverre Rabbelier
2009-03-18 9:54 ` Michael J Gruber
2009-03-18 14:52 ` Marcel M. Cary
2009-03-18 21:02 ` Marcel M. Cary
2009-04-10 12:17 ` Olivier Goffart
2009-04-10 12:37 ` Michael Witten
2009-04-10 12:41 ` Michael Witten
2009-04-10 18:21 ` Johannes Schindelin
2009-04-10 18:50 ` Michael Witten [this message]
2009-04-10 18:54 ` Sverre Rabbelier
2009-04-10 19:04 ` Michael Witten
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=b4087cc50904101150i31f1bbfdre73bec44dac580eb@mail.gmail.com \
--to=mfwitten@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=ogoffart@kde.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).