From: Matthieu Moy <Matthieu.Moy@imag.fr>
To: Marco Costalba <mcostalba@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: WISH: Extending git commit --amend
Date: Fri, 29 May 2009 10:10:09 +0200 [thread overview]
Message-ID: <vpqprds2uu6.fsf@bauges.imag.fr> (raw)
In-Reply-To: <e5bfff550905282348gf29aa16o6eec88423bb5ce23@mail.gmail.com> (Marco Costalba's message of "Fri\, 29 May 2009 08\:48\:46 +0200")
Marco Costalba <mcostalba@gmail.com> writes:
> Would be possible to extend git commit --amend so to automate the
> above sequence ? Or does perhaps exists a better sequence to change
> (actually simulate the change of) log message of an inner revision?
git rebase -i E^
Then, change a "pick" with a "edit" wherever you want.
(Perhaps the doc of commit --amend could say "to amend a previous
commit, you may want to look at the 'edit' command of 'git rebase
-i'"?)
--
Matthieu
next prev parent reply other threads:[~2009-05-29 8:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-29 6:48 WISH: Extending git commit --amend Marco Costalba
2009-05-29 8:09 ` Eric Raible
2009-05-29 8:10 ` Matthieu Moy [this message]
2009-05-29 10:39 ` Marco Costalba
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=vpqprds2uu6.fsf@bauges.imag.fr \
--to=matthieu.moy@imag.fr \
--cc=git@vger.kernel.org \
--cc=mcostalba@gmail.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.
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).