Re: slightly confusing message

Leon George writes: > On 20/02/17 21:19, Junio C Hamano wrote: >> This sounds vaguely familiar and indeed I think it is this one: >> https://public-inbox.org/git/CAEnOLdvG=sokfxej_plmamgj_8osc+28tsg+pbflltr+zlc...@mail.gmail.com/ >> which was from late last year. > Which means I should have found

Re: slightly confusing message

Hello and thank you for your time. On 20/02/17 21:19, Junio C Hamano wrote: > This sounds vaguely familiar and indeed I think it is this one: > https://public-inbox.org/git/CAEnOLdvG=sokfxej_plmamgj_8osc+28tsg+pbflltr+zlc...@mail.gmail.com/ > which was from late last year. Which means I should hav

Re: slightly confusing message

Leon George writes: > Every once in a while this: > > £ git add -p . > warning: empty strings as pathspecs will be made invalid in upcoming > releases. please use . instead if you meant to match all paths > No changes. > > It seems to happen only when there are no more modified files and git > st

slightly confusing message

Hey, you lovely people <3 Every once in a while this: £ git add -p . warning: empty strings as pathspecs will be made invalid in upcoming releases. please use . instead if you meant to match all paths No changes. It seems to happen only when there are no more modified files and git still works w