From: Junio C Hamano <gitster@pobox•com>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp•fr>
Cc: Guillaume Pages <guillaume.pages@ensimag•grenoble-inp.fr>,
Paul Tan <pyokagan@gmail•com>,
Antoine Delaite <antoine.delaite@ensimag•grenoble-inp.fr>,
Remi Galan <remi.galan-alfonso@ensimag•grenoble-inp.fr>,
Remi Lespinet <remi.lespinet@ensimag•grenoble-inp.fr>,
Louis-Alexandre Stuber
<louis--alexandre.stuber@ensimag•grenoble-inp.fr>,
git@vger•kernel.org
Subject: Re: [RFC/PATCH v2] create a skeleton for the command git rebase --status
Date: Thu, 28 May 2015 12:50:58 -0700 [thread overview]
Message-ID: <xmqq382gh465.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <vpqlhg8pk1o.fsf@anie.imag.fr> (Matthieu Moy's message of "Thu, 28 May 2015 21:40:51 +0200")
Matthieu Moy <Matthieu.Moy@grenoble-inp•fr> writes:
> 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)
Not really. How would you decide if 7f9a792 is worth keeping or
rebase is better be aborted without knowing where you are?
> I like the output of "git status" to be concise.
Sure, as long as concise and useful, I am all for it. The above
however does not show anything I already know in my prompt. I would
say no thanks to "concise and useless".
> OTOH, there are tons of information in .git/rebase-merge/ that
> could be displayed to the user.
Surely, that is why "git status" during a rebase should show them.
next prev parent reply other threads:[~2015-05-28 19:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-28 14:20 [RFC/PATCH v2] create a skeleton for the command git rebase --status Guillaume Pagès
2015-05-28 15:39 ` Matthieu Moy
[not found] ` <CACRoPnRa1wrOJr=wGnR4NayZfe2yJ4F7Abv_sjqRpgQnicxm1g@mail.gmail.com>
2015-05-28 15:43 ` Guillaume Pages
2015-05-28 15:53 ` Matthieu Moy
2015-05-28 18:18 ` Junio C Hamano
2015-05-28 19:40 ` Matthieu Moy
2015-05-28 19:50 ` Junio C Hamano [this message]
2015-05-29 10:40 ` Guillaume Pages
2015-05-29 15:00 ` Matthieu Moy
2015-05-29 15:44 ` Junio C Hamano
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=xmqq382gh465.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=Matthieu.Moy@grenoble-inp$(echo .)fr \
--cc=antoine.delaite@ensimag$(echo .)grenoble-inp.fr \
--cc=git@vger$(echo .)kernel.org \
--cc=guillaume.pages@ensimag$(echo .)grenoble-inp.fr \
--cc=louis--alexandre.stuber@ensimag$(echo .)grenoble-inp.fr \
--cc=pyokagan@gmail$(echo .)com \
--cc=remi.galan-alfonso@ensimag$(echo .)grenoble-inp.fr \
--cc=remi.lespinet@ensimag$(echo .)grenoble-inp.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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