Re: [RFC/PATCH v2] create a skeleton for the command git rebase --status
- From
Matthieu Moy <matthieu.moy@grenoble-inp.fr>
- Date
- May 28, 2015, 19:40 UTC
- Message-ID
- <vpqlhg8pk1o.fsf@anie.imag.fr>
- In-Reply-To
- <xmqqtwuwh8fv.fsf@gitster.dls.corp.google.com>
Junio C Hamano <gitster@pobox.com> writes:
> If this topic enhances 'git status' with the in-progress rebase > information, I'd view it as turning 'git status' from 'a more or > less useless command during rebase' to 'a useful command'.
For day-to-day operations, what we already have in status already qualifies as 'useful command' to me:
$ git status rebase in progress; onto 7f9a792 You are currently rebasing branch 'master' on '7f9a792'. (fix conflicts and then run "git rebase --continue") (use "git rebase --skip" to skip this patch) (use "git rebase --abort" to check out the original branch)
I like the output of "git status" to be concise. OTOH, there are tons of information in .git/rebase-merge/ that could be displayed to the user.
-- Matthieu Moy http://www-verimag.imag.fr/~moy/