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

Re: New feature discussion: git rebase --status

From
Thomas Rast <trast@inf.ethz.ch>
Date
Jun 11, 2013, 12:40 UTC
Message-ID
<871u8895xh.fsf@linux-k42r.v.cablecom.net>
In-Reply-To
<fb379a75c6c1af6dcff2e65bef1f1836@ensibm.imag.fr>
Mathieu Liénard--Mayor <mathieu.lienard--mayor@ensimag.fr> writes:
Show 31 quoted lines
> (Got the idea from:
> https://git.wiki.kernel.org/index.php/SmallProjectsIdeas#git_rebase_--status)
>
> When in the middle of a rebase, users can be easily confused about
> what to do, or where they are in the rebase process.
>
> All the information is available in .git/rebase-merge/, but I believe
> it would be helpful to have a command (for example 'git rebase
> --status') which would explicitely indicate the state of the process.
>
> For instance, the output could look like:
>
> $ git rebase --status
> Rebasing my_last_commit onto base_commit
> Already applied 2 patches:
> 	b170635... my_commit_message
> 	b170635... my_commit_message
> Currently applying b170635... my_commit_message
> 2 patches left to apply:
> 	b170635... my_commit_message
> 	b170635... my_commit_message
>
>
> Another nice thing could be to improve the output of 'git status' by
> saying the number of patches left to apply.
> As an example, it could say:
> 	You are currently rebasing (patch 3/5).
>
> What do you think?
> Does the name rebase --status seem appropriate?
> Should the output be providing more/less information?

I think a worthy goal would be to arrange things such that the "here's what you do next" messages are shared between --status and the code that stops. I.e., the same code should generate

  When you have resolved this problem, run "git rebase --continue".                                      
  If you prefer to skip this patch, run "git rebase --skip" instead.                                     
  To check out the original branch and stop rebasing, run "git rebase --abort".

in both cases. Naturally --status should also explain how it got into this state, as you outlined above.

-- 
Thomas Rast
trast@{inf,student}.ethz.ch
Previous: Mathieu Liénard--MayorNext: John Keeping
Message 2 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.