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 wonderfully otherwise - just wanted to let you know.
enjoy your weeks :-)
Junio C HamanoRe: slightly confusing message
Leon George <leon@georgemail.eu> 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 > still works wonderfully otherwise - just wanted to let you know.
This sounds vaguely familiar and indeed I think it is this one:
https://public-inbox.org/git/CAEnOLdvG=SoKFxeJ_pLmamGj_8osC+28TSg+pbFLLTr+ZLcpQA@mail.gmail.com/
which was from late last year.
I suspect that the issue may already be fixed at the tip of 'master' (aka Git 2.12-rc2).
Thanks.
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+ZLcpQA@mail.gmail.com/ > which was from late last year.
Which means I should have found it before bothering you.
> I suspect that the issue may already be fixed at the tip of 'master' > (aka Git 2.12-rc2).
You're absolutely right. Took a while to build, but here goes:
£ git gitss ?? test £ git --version git version 2.11.0 £ 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. £ git --version git version 2.12.0-rc2 £ git add -p . No changes.
Splendid!
have a wonderfull day :-)
Junio C HamanoRe: slightly confusing message
Leon George <leon@georgemail.eu> 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+ZLcpQA@mail.gmail.com/ >> which was from late last year. > Which means I should have found it before bothering you.
It means no such thing, though. It just means that I happen to be more familiar with what has gone on the development recently than you were ;-)
>> I suspect that the issue may already be fixed at the tip of 'master' >> (aka Git 2.12-rc2). > You're absolutely right. Took a while to build, but here goes: > ... > Splendid!
Thanks for confirming.