0

I have an old commit message that I want to edit, but in rebase I can get only the last 35 commands

Joseph
  • 3
  • 3
  • Where did you take that 35 commands limit? I have never heard of it. And I just tested with rebase 60 commits back with no problem. – Igal S. May 15 '16 at 11:44
  • I write: "git rebase -i HEAD~60" and get "fatal: Needed a single revision" – Joseph May 15 '16 at 13:10
  • I suggest you try `HEAD^60` - There is a difference. You can read about it here: http://stackoverflow.com/questions/2221658/whats-the-difference-between-head-and-head-in-git – Igal S. May 15 '16 at 13:22

2 Answers2

0

Locate the commit you want to change message for and copy it's SHA-1. Then do git rebase -i <SHA-1>~1.

madhead
  • 31,729
  • 16
  • 153
  • 201
0

Summary of solution:

OP used git rebase -i HEAD~60 to locate the commit to rebase on.

The correct way to use it is:

git rebase -i HEAD^60

It is worth reading the difference between ~ and ^ in: What's the difference between HEAD^ and HEAD~ in Git?

Community
  • 1
  • 1
Igal S.
  • 13,146
  • 5
  • 30
  • 48