diff options
| author | Junio C Hamano <gitster@pobox.com> | 2017-11-06 04:11:29 (GMT) |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2017-11-06 04:11:29 (GMT) |
| commit | 728c57380338eed1aaad6047046ca71826e8066c (patch) | |
| tree | d4b2f8372dbb16a7bbca29e73cb682f495cc140b /repository.c | |
| parent | e4db47e6a038adcde36ef6305a15d3d7ee49487c (diff) | |
| parent | 9e4e8a64c2b9043b7ae2b6476efd9214c6738505 (diff) | |
| download | git-728c57380338eed1aaad6047046ca71826e8066c.zip git-728c57380338eed1aaad6047046ca71826e8066c.tar.gz git-728c57380338eed1aaad6047046ca71826e8066c.tar.bz2 | |
Merge branch 'ex/deprecate-empty-pathspec-as-match-all'
The final step to make an empty string as a pathspec element
illegal. We started this by first deprecating and warning a
pathspec that has such an element in 2.11 (Nov 2016).
Hopefully we can merge this down to the 'master' by the end of the
year? A deprecation warning period that is about 1 year does not
sound too bad.
* ex/deprecate-empty-pathspec-as-match-all:
pathspec: die on empty strings as pathspec
t0027: do not use an empty string as a pathspec element
Diffstat (limited to 'repository.c')
0 files changed, 0 insertions, 0 deletions