Edit File: git-rebase-todo.backup
pick 7409bda430086698fc0c7f82137d02eb58d1a1bd server pick 0ccee0aa78c97fe985c2e5f6988d34f3c7633fa2 server pick 3610c2745a0ef8b3aa816e8658742e6d675069a4 server pick a46df85e802c8351631685f74c928fccd8e62ae5 server pick d556b6aff3dabe336b08edfd7011219d7fbe5cd7 server # Rebase c4115f9f..d556b6af onto c4115f9f (5 commands) # # Commands: # p, pick <commit> = use commit # r, reword <commit> = use commit, but edit the commit message # e, edit <commit> = use commit, but stop for amending # s, squash <commit> = use commit, but meld into previous commit # f, fixup [-C | -c] <commit> = like "squash" but keep only the previous # commit's log message, unless -C is used, in which case # keep only this commit's message; -c is same as -C but # opens the editor # x, exec <command> = run command (the rest of the line) using shell # b, break = stop here (continue rebase later with 'git rebase --continue') # d, drop <commit> = remove commit # l, label <label> = label current HEAD with a name # t, reset <label> = reset HEAD to a label # m, merge [-C <commit> | -c <commit>] <label> [# <oneline>] # create a merge commit using the original merge commit's # message (or the oneline, if no original merge commit was # specified); use -c <commit> to reword the commit message # u, update-ref <ref> = track a placeholder for the <ref> to be updated # to this position in the new commits. The <ref> is # updated at the end of the rebase # # These lines can be re-ordered; they are executed from top to bottom. # # If you remove a line here THAT COMMIT WILL BE LOST. # # However, if you remove everything, the rebase will be aborted. #
Back to File Manager