From: Jakub Narebski <jnareb@gmail.com>
To: bill lam <cbill.lam@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: how to edit commit message in history
Date: Fri, 16 Jan 2009 03:18:37 -0800 (PST) [thread overview]
Message-ID: <m34ozzzegn.fsf@localhost.localdomain> (raw)
In-Reply-To: <20090116035714.GA6984@b2j>
bill lam <cbill.lam@gmail.com> writes:
> I made some typos in commit messages, how to edit them without
> affecting everything else?
If it is last commit that you want to edit, and if you didn't publish
this commit to soem public repository, you can simply use
$ git commit --amend
If the commit is deeper in history, use "git rebase --interactive".
If you published commit, you are out of luck.
See http://git.or.cz/gitwiki/GitTips
--
Jakub Narebski
Poland
ShadeHawk on #git
prev parent reply other threads:[~2009-01-16 11:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-16 3:57 how to edit commit message in history bill lam
2009-01-16 4:09 ` Jike Song
2009-01-16 4:31 ` thestar
2009-01-16 11:18 ` Jakub Narebski [this message]
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=m34ozzzegn.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=cbill.lam@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).