After a few hours, here's a quick summary of your opinions:
-'git status' should be the command to display the information instead
of a --status flag
-the SHA1 of the patch being applied currently is a very important
information
-displaying how we got to this state would be nice
I had in mind a slight change in the current status message, just to
include the SHA1 and where we're at in the rebasing. It would look like
this:
$ git status
# HEAD detached from ecb9f3e
# You are currently editing a832578... my_commit_message [3/5] while
rebasing.
# (use "git commit --amend" to amend the current commit)
# (use "git rebase --continue" once you are satisfied with your
changes)
# ......
# ......
Now, I'm not sure if we should always display the list of commits
already applied and those left to apply. What I mean is that maybe it
would be better to make status require a flag to display the two lists.
Something like (not sure about the flag's name):
$ git status --rebase-state
# HEAD detached from ecb9f3e
# Already applied 2 patches:
# b170635... my_commit_message
# b170635... my_commit_message
# You are currently editing a832578... my_commit_message [3/5] while
rebasing.
# 2 patches left to apply:
# b170635... my_commit_message
# b170635... my_commit_message
# (use "git commit --amend" to amend the current commit)
# (use "git rebase --continue" once you are satisfied with your
changes)
# ......
# ......
What do you guys think ?
--
Mathieu Liénard--Mayor,
2nd year at Grenoble INP - ENSIMAG
(+33)6 80 56 30 02
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
