Hi Junio,
On Fri, 22 Jan 2016, Junio C Hamano wrote:
> Matthieu Moy writes:
>
> > Johannes Schindelin writes:
> >
> >> wt-status.c | 22 +++---
> >> 1 file changed, 15 insertions(+), 7 deletions(-)
> >
> > Looks good to me. You may want to add a test by overriding $EDITOR to a
Matthieu Moy writes:
> Johannes Schindelin writes:
>
>> wt-status.c | 22 +++---
>> 1 file changed, 15 insertions(+), 7 deletions(-)
>
> Looks good to me. You may want to add a test by overriding $EDITOR to a
> script doing "git status >actual" if you want to have fun with testi
Hi Matthieu,
On Fri, 22 Jan 2016, Matthieu Moy wrote:
> Johannes Schindelin writes:
>
> > wt-status.c | 22 +++---
> > 1 file changed, 15 insertions(+), 7 deletions(-)
>
> Looks good to me. You may want to add a test by overriding $EDITOR to a
> script doing "git status >actua
Johannes Schindelin writes:
> wt-status.c | 22 +++---
> 1 file changed, 15 insertions(+), 7 deletions(-)
Looks good to me. You may want to add a test by overriding $EDITOR to a
script doing "git status >actual" if you want to have fun with testing.
Thanks,
--
Matthieu Moy
ht
From: Junio C Hamano
Some developers might want to call `git status` in a working
directory where they just started an interactive rebase, but the
edit script is still opened in the editor.
Let's show a meaningful message in such cases.
[jes: suppressed the "No commands remaining" message when
5 matches
Mail list logo
