From: Guillaume Pages <guillaume.pages@ensimag.grenoble-inp.fr>
Date: Thu, 28 May 2015 15:43:09 GMT
Subject: Re: [RFC/PATCH v2] create a skeleton for the command git rebase --status
Message-ID: <1141577560.115469.1432827789020.JavaMail.zimbra@ensimag.grenoble-inp.fr>
In-Reply-To: <CACRoPnRa1wrOJr=wGnR4NayZfe2yJ4F7Abv_sjqRpgQnicxm1g@mail.gmail.com>


Hi, 

"Paul Tan" <pyokagan@gmail.com> : 
> I haven't kept up with the discussion, but I'm wondering: since you 
> need the functionality in wt-status.c, why not implement it in git 
> status? In fact, git-status already shows if there is a rebase in 
> progress, so why not extend it to say which patch/todo line the rebase 
> stopped on? It feels much more natural to me to use git-status to 
> check the status of the rebase, instead of git rebase --status. 
> Thanks, Paul 

It's a question I have asked myself but since git rebase --status will 
certainly display more information maybe it's better to separate the 
two commands, and to indicate the user that git rebase --status exists 
in git status during a rebase. If we choose to use git status, it 
could be an option to display the full information since it currently 
gives very few information. I'm not sure what -verbose does but it 
could be its role. 

Thanks, 

Guillaume Pagès