On Tuesday, December 10, 2013 9:52:21 PM UTC+1, Michael Hatherly wrote:
> I've updated to git 22.214.171.124 from 126.96.36.199 today.
> Previously when running `git add --all` or `git add .` in an *empty*directory
> would be no shell output.
> Now running either of these commands results in `fatal: pathspec '.' did
> not match any files` as output.
> My question: Is this expected behaviour now, and, if so, where would I be
> able to find any news announcing/discussing
This sounds like a bit of a corner-case feature (albeit it is a useful
warning, so it's probably intended), so perhaps it was not flagged high
among the release notes, which in any case you can find on the Git
development mailing list . The maintainer also keeps a more
press-friendly overview on his blog . Of course, to see all the details,
you should look at the commit history of Git itself.
If you want to get earlier warning on what features are coming in future
versions of Git, you can track the "What's cooking in git.git" mails that
the maintainer sends out on the mailing list on a regular basis.
> So far I've managed to find
> which does
> mention a change to `git add` in the *2.0 section* but nothing in *changes
> since 1.8.4* section.
You'll see that in 1.8.5 git add received some major changes in preparation
for 2.0, spitting out a lot more warnings, and acting differently when no
pathspec is given. My guess is that the change you've observed was made as
part of these changes.
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/groups/opt_out.