delta/libgit2.git/tests/stash, branch ethomson/https_proxy github.com: libgit2/libgit2.git object_type: use new enumeration names 2018-12-01T11:54:57+00:00 Edward Thomson ethomson@edwardthomson.com 2018-11-28T14:26:57+00:00 168fe39bea3368972a8b1a33d5908e73bc790c18 Use the new object_type enumeration names within the codebase. 
Use the new object_type enumeration names within the codebase.
Merge pull request #4702 from tiennou/fix/coverity 2018-07-20T10:56:49+00:00 Patrick Steinhardt ps@pks.im 2018-07-20T10:56:49+00:00 0652abaaeaff768e78a65464e59bd1896ce2f6ce Assorted Coverity fixes 
Assorted Coverity fixes
 treewide: remove use of C++ style comments 2018-07-13T06:25:12+00:00 Patrick Steinhardt ps@pks.im 2018-06-25T09:56:52+00:00 9994cd3f0ffcd7b28d26c82ecb6564bc4072dc2a C++ style comment ("//") are not specified by the ISO C90 standard and thus do not conform to it. While libgit2 aims to conform to C90, we did not enforce it until now, which is why quite a lot of these non-conforming comments have snuck into our codebase. Do a tree-wide conversion of all C++ style comments to the supported C style comments to allow us enforcing strict C90 compliance in a later commit. 
C++ style comment ("//") are not specified by the ISO C90 standard and
thus do not conform to it. While libgit2 aims to conform to C90, we did
not enforce it until now, which is why quite a lot of these
non-conforming comments have snuck into our codebase. Do a tree-wide
conversion of all C++ style comments to the supported C style comments
to allow us enforcing strict C90 compliance in a later commit.
tests: add missing cl_git_pass to tests 2018-07-06T20:24:21+00:00 Etienne Samson samson.etienne@gmail.com 2018-07-01T10:04:27+00:00 8455a2709f8c2fabf0df775a193b9ef72bb21e43 Reported by Coverity, CID 1393678-1393697. 
Reported by Coverity, CID 1393678-1393697.
 Fix last references to deprecated git_buf_free 2018-06-18T11:05:08+00:00 Sven Strickroth email@cs-ware.de 2018-06-18T11:05:08+00:00 b5818ddabd9273c71dfd248da92d1d13ac2ace42 Signed-off-by: Sven Strickroth <email@cs-ware.de> 
Signed-off-by: Sven Strickroth <email@cs-ware.de>
Merge pull request #4436 from pks-t/pks/packfile-stream-free 2018-06-11T17:26:22+00:00 Edward Thomson ethomson@edwardthomson.com 2018-06-11T17:26:22+00:00 3be7301151e44537d2423386dc71f1d3e496c664 pack: rename `git_packfile_stream_free` 
pack: rename `git_packfile_stream_free`
 stash test: free the commit 2018-06-11T16:11:36+00:00 Edward Thomson ethomson@edwardthomson.com 2018-06-11T16:11:36+00:00 9621281304e5b1e418c09f3830e7fcdc7e990e82 






Convert usage of `git_buf_free` to new `git_buf_dispose`
2018-06-10T17:34:37+00:00

Patrick Steinhardt
ps@pks.im

2018-02-08T11:14:48+00:00

ecf4f33a4e327a91496f72816f9f02d923e5af05












stash test: free the reference
2018-06-10T16:21:58+00:00

Edward Thomson
ethomson@edwardthomson.com

2018-06-10T16:21:43+00:00

123f01f07b009adaab3239604298579642f69183












Fix stash save bug with fast path index check
2018-06-06T18:45:56+00:00

David Turner
novalis@novalis.org

2018-06-04T16:56:08+00:00

5a7d454bf657fdf4d726f2319bf554ffd4486ed3

If the index contains stat data for a modified file, and the file is
not racily dirty, and there exists an untracked working tree directory
alphabetically after that file, and there are no other changes to the
repo, then git_stash_save would fail. It would confuse the untracked
working tree directory for the modified file, because they have the
same sha: zero.  The wt directory has a sha of zero because it's a
directory, and the file would have a zero sha because we wouldn't read
the file -- we would just know that it doesn't match the index.  To
fix this confusion, we simply check mode as well as SHA.





If the index contains stat data for a modified file, and the file is
not racily dirty, and there exists an untracked working tree directory
alphabetically after that file, and there are no other changes to the
repo, then git_stash_save would fail. It would confuse the untracked
working tree directory for the modified file, because they have the
same sha: zero.  The wt directory has a sha of zero because it's a
directory, and the file would have a zero sha because we wouldn't read
the file -- we would just know that it doesn't match the index.  To
fix this confusion, we simply check mode as well as SHA.