From: Marco Costalba <mcostalba@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: WISH: Extending git commit --amend
Date: Fri, 29 May 2009 08:48:46 +0200 [thread overview]
Message-ID: <e5bfff550905282348gf29aa16o6eec88423bb5ce23@mail.gmail.com> (raw)
Form current documentation
--amend
Used to amend the tip of the current branch. Prepare the tree
object you would want to replace the latest commit as usual (this
includes the usual -i/-o and explicit paths), and the commit log
editor is seeded with the commit message from the tip of the current
branch. The commit you create replaces the current tip — if it was a
merge, it will have the parents of the current tip as parents — so the
current top commit is discarded.
It is a rough equivalent for:
$ git reset --soft HEAD^
$ ... do something else to come up with the right tree ...
$ git commit -c ORIG_HEAD
but can be used to amend a merge commit.
I find myself wanting to amend not tip of the branch, but an older
commit (typically to change log message). As example if I have this
D---E---F---G master
And I want to amend revision E currently I do
$ git branch tmp
$ git reset E
$ git commit --amend
$ git rebase tmp master
$ git branch -d tmp
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?
Thanks in advance
Marco
next reply other threads:[~2009-05-29 6:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-29 6:48 Marco Costalba [this message]
2009-05-29 8:09 ` WISH: Extending git commit --amend Eric Raible
2009-05-29 8:10 ` Matthieu Moy
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=e5bfff550905282348gf29aa16o6eec88423bb5ce23@mail.gmail.com \
--to=mcostalba@gmail.com \
--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).