IMO, if you put an empty string you would be implying the same as
with a dot (git add . ).
The important thing is that git add without a pathspec returns an
error, as it has always done, mainly because it people tend to work
without gitignoring all the files they should, and allowing such
Hello,
I first asked on stackoverflow
(http://stackoverflow.com/questions/26933761/python-sh-module-and-git-try-to-add-more-files-then-in-command/26934517#26934517)
about this behaviour.
Then on the conversation that happened on the git-users mailing list
other agreed that this behaviour is
Guilherme guibuf...@gmail.com writes:
Steps to reproduce:
In bash (not sure this is bash specific) do:
git add ''
(that's to apostrophes, an empty argument)
Results
same as doing git add .
Expected
no files added or error about not finding file ''
The argument to git add is a pathspec,
Andreas Schwab sch...@linux-m68k.org writes:
The argument to git add is a pathspec, and the empty pathspec matches
all files.
Err, why does the empty pathspec match all files? Isn't that a bug?
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
--
To unsubscribe from this list: send the line
Matthieu Moy matthieu@grenoble-inp.fr writes:
Andreas Schwab sch...@linux-m68k.org writes:
The argument to git add is a pathspec, and the empty pathspec matches
all files.
Err, why does the empty pathspec match all files? Isn't that a bug?
That is debatable.
cd Documentation
5 matches
Mail list logo
