On Sat, Jul 21, 2012 at 07:43:31AM +0530, Rustom Mody wrote:
> > I suspect that you are in "rebase mode". That is, you're in the middle of
> > rewriting som history, and Git is waiting for you to type things like "git
> > rebase --abort" or "git rebase --continue". If you just want to get out of
> > this mode, I reckon also a "git reset --hard master" should get you back to
> > how you left things in master branch.
> It is said about vi: The text editor with two modes... one that beeps and
> one that corrupts your file
> Currently I have the same expertise at git that I had when first learning
> vi (many years ago)
> Can I find a summary of 'git modes' somewhere?
Please stop inventing bullshit. It's natural, that when you're starting
an interactive (!) rebase and then tell git you want to edit a commit,
Git has to be told when you're done with your edits. And when Git
stops carrying rebase steps at the commit you told it you want to edit,
it tells you in clear words what to do when you're done:
foo% git rebase -i HEAD~3
Stopped at 183fe3c... 3rd commit
You can amend the commit now, with
git commit --amend
Once you are satisfied with your changes, run
git rebase --continue
You did not pay attention to this (quite wordy) message and are now
trying to make up sarcastic jokes. Please don't. Start from reading
`git rebase` manual, in particular the --abort option to `git rebase`.
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 firstname.lastname@example.org.
To unsubscribe from this group, send email to
For more options, visit this group at