Open vise890 opened 7 years ago
Hi, I think that was intentional. It's just meant to be a tip to show that environment variables are available for the different numbers.
It's not too important though, would be happy to remove that
Hmm I'm confused. The tip makes sense when there are actually files staged or untracked or whatever. But in this case there aren't and the message No changes (working directory clean)
is gone.
@ghthor so what should we do? i'm a bit unhappy with the new output, i liked to see "working dir clean".
I'd like to bring back the old output, I haven't looked at the commit you referenced yet
On Feb 12, 2017 3:51 PM, "Martino Visintin" notifications@github.com wrote:
@ghthor https://github.com/ghthor so what should we do? i'm a bit unhappy with the new output, i liked to see "working dir clean".
— You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/scmbreeze/scm_breeze/issues/233#issuecomment-279247792, or mute the thread https://github.com/notifications/unsubscribe-auth/AAJyKirIB3amv9WfZcHIuasGdiTqPadVks5rb3DEgaJpZM4L6MlK .
How it should / used to look
How it looks now:
git bisect
indicates that the first bad commit was23e99709daf5c35b755841dd6457913c26839739
which was recently merged