On Jul 27, 1:53 am, Jeenu <gro...@jeenuv.otherinbox.com> wrote:
> On Jul 27, 7:33 am, misha680 <misha...@gmail.com> wrote:
> > Dear All:
> > I have heard great things about this
> > list:http://kerneltrap.org/mailarchive/git/2008/6/4/2025514
> > I love git rebase --interactive, but would like to have the same
> > functionality for editing the actual diffs themselves (e.g., two
> > commits back).
> Not sure if this is what you wanted:
> * git rebase -i some_old_commit
> * Change 'pick' to 'edit' for commits that you're interested in
> * When git rebase pauses for you to edit commit, do 'git reset'
> leaving your files unstaged
> * Then invoke 'git add -e', and you should be able to edit your
Wow thank you.
That almost seems to do the trick.
However, it seems when I do git reset I get an empty commit.
If I do something like:
git reset HEAD^
my commit becomes non-empty, but then I am obviously on a different
commit when I do
git commit --amend
Any hints? I am guessing there might be an extra parameter or smthng
to git reset.
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To post to this group, send email to git-us...@googlegroups.com.
To unsubscribe from this group, send email to
For more options, visit this group at