git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: New feature discussion: git rebase --status

From
Célestin Matte <celestin.matte@ensimag.fr>
Date
Jun 12, 2013, 11:12 UTC
Message-ID
<51B857B0.5030603@ensimag.fr>
In-Reply-To
<fa9c12a81ef2e92ba75dd1271d9e0b2d@ensibm.imag.fr>
Le 12/06/2013 12:17, Mathieu Liénard--Mayor a écrit :
Show 21 quoted lines
> 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 ?

I agree. When you're in the process of rebasing a big list of commits, it would produce a lot of not-so-useful output, when what you want to see is, most of the time, which commit you are currently editing. So, in my opinion, whole lists should not be displayed by default.

Now, if I could suggest an improvement over that list: when you rebase some commits, I'm quite sure the history of what you already did is stored somewhere since you can revert it which git rebase --abort. It would be nice to improve that list by displaying these informations, like:

$ git status --rebase-state # HEAD detached from ecb9f3e # Already applied 4 patches: # b170635... my_commit_message # b170635... my_commit_message # new: b170635... my_commit_message # modified: b170635... my_commit_message # reworded: b170635... my_commit_message # You are currently editing a832578... my_commit_message [5/8] 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) # ...... # ......

I have no idea how complicated it would be to do that, though. What do you think?

-- 
Célestin Matte
Previous: Mathieu Liénard--MayorNext: Mathieu Liénard--Mayor
Message 8 of 16 in “New feature discussion: git rebase --status”
  1. Mathieu Liénard--MayorJun 11, 2013
  2. Thomas RastJun 11, 2013
  3. John KeepingJun 11, 2013
  4. Matthieu MoyJun 11, 2013
  5. Hilco WijbengaJun 11, 2013
  6. Linus TorvaldsJun 11, 2013
  7. Mathieu Liénard--MayorJun 12, 2013
  8. Célestin MatteJun 12, 2013
  9. Mathieu Liénard--MayorJun 12, 2013
  10. Antoine PelisseJun 12, 2013
  11. Junio C HamanoJun 12, 2013
  12. Antoine PelisseJun 13, 2013
  13. Mathieu Liénard--MayorJun 13, 2013
  14. Matthieu MoyJun 12, 2013
  15. John KeepingJun 12, 2013
  16. Mathieu Liénard--MayorJun 12, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.