From: "Mathieu Liénard--Mayor" <mathieu.lienard--mayor@ensimag.fr>
To: <git@vger.kernel.org>
Cc: <Mathieu.Lienard--Mayor@ensimag.imag.fr>,
<Jorge-Juan.Garcia-Garcia@ensimag.imag.fr>,
<Matthieu.Moy@grenoble-inp.fr>
Subject: New feature discussion: git rebase --status
Date: Tue, 11 Jun 2013 14:35:29 +0200 [thread overview]
Message-ID: <fb379a75c6c1af6dcff2e65bef1f1836@ensibm.imag.fr> (raw)
(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?
Thanks =]
--
Mathieu Liénard--Mayor,
2nd year at Grenoble INP - ENSIMAG
(+33)6 80 56 30 02
next reply other threads:[~2013-06-11 12:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-11 12:35 Mathieu Liénard--Mayor [this message]
2013-06-11 12:40 ` New feature discussion: git rebase --status Thomas Rast
2013-06-11 12:55 ` John Keeping
2013-06-11 13:19 ` Matthieu Moy
2013-06-11 17:18 ` Hilco Wijbenga
2013-06-11 17:23 ` Linus Torvalds
2013-06-12 10:17 ` Mathieu Liénard--Mayor
2013-06-12 11:12 ` Célestin Matte
2013-06-12 11:23 ` Mathieu Liénard--Mayor
2013-06-12 12:28 ` Antoine Pelisse
[not found] ` <CAH_OBifOeSSWB-LPT=Zv2AGEf5+nTh7yxE-1ijD0snFp3RS8Dw@mail.gmail.com>
2013-06-12 12:50 ` Mathieu Liénard--Mayor
2013-06-12 22:19 ` Junio C Hamano
2013-06-13 5:52 ` Antoine Pelisse
2013-06-13 12:19 ` Mathieu Liénard--Mayor
2013-06-12 12:41 ` Matthieu Moy
2013-06-12 12:52 ` John Keeping
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fb379a75c6c1af6dcff2e65bef1f1836@ensibm.imag.fr \
--to=mathieu.lienard--mayor@ensimag.fr \
--cc=Jorge-Juan.Garcia-Garcia@ensimag.imag.fr \
--cc=Mathieu.Lienard--Mayor@ensimag.imag.fr \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).