delta/libgit2.git/tests/diff, branch ethomson/no_void github.com: libgit2/libgit2.git diff: make patchid computation work with all types of commits. 2019-11-28T13:17:50+00:00 Gregory Herrero gregory.herrero@oracle.com 2019-11-07T13:10:00+00:00 ece5bb5e7d6e35e50096bac3d7bf17342daaec77 Current implementation of patchid is not computing a correct patchid when given a patch where, for example, a new file is added or removed. Some more corner cases need to be handled to have same behavior as git patch-id command. Add some more tests to cover those corner cases. Signed-off-by: Gregory Herrero <gregory.herrero@oracle.com> 
Current implementation of patchid is not computing a correct patchid
when given a patch where, for example, a new file is added or removed.
Some more corner cases need to be handled to have same behavior as git
patch-id command.
Add some more tests to cover those corner cases.

Signed-off-by: Gregory Herrero <gregory.herrero@oracle.com>
patch_parse: handle patches without extended headers 2019-10-16T20:53:29+00:00 Denis Laxalde denis@laxalde.org 2019-10-16T20:11:33+00:00 11de594f85479e4804b07dc4f7b33cfe9212bea0 Extended header lines (especially the "index <hash>..<hash> <mode>") are not required by "git apply" so it import patches. So we allow the from-file/to-file lines (--- a/file\n+++ b/file) to directly follow the git diff header. This fixes #5267. 
Extended header lines (especially the "index <hash>..<hash> <mode>") are
not required by "git apply" so it import patches. So we allow the
from-file/to-file lines (--- a/file\n+++ b/file) to directly follow the
git diff header.

This fixes #5267.
patch_parse: handle patches with new empty files 2019-09-28T13:52:25+00:00 Denis Laxalde denis@laxalde.org 2019-09-28T13:52:25+00:00 b61810bf1ff1007bc0a5d8e47362a735f2ff1f0b Patches containing additions of empty files will not contain diff data but will end with the index header line followed by the terminating sequence "-- ". We follow the same logic as in cc4c44a and allow "-- " to immediately follow the index header. 
Patches containing additions of empty files will not contain diff data
but will end with the index header line followed by the terminating
sequence "-- ". We follow the same logic as in cc4c44a and allow "-- "
to immediately follow the index header.
fileops: rename to "futils.h" to match function signatures 2019-07-20T17:11:20+00:00 Patrick Steinhardt ps@pks.im 2019-06-29T07:17:32+00:00 e54343a4024e75dfaa940e652c2c9799d33634b2 Our file utils functions all have a "futils" prefix, e.g. `git_futils_touch`. One would thus naturally guess that their definitions and implementation would live in files "futils.h" and "futils.c", respectively, but in fact they live in "fileops.h". Rename the files to match expectations. 
Our file utils functions all have a "futils" prefix, e.g.
`git_futils_touch`. One would thus naturally guess that their
definitions and implementation would live in files "futils.h" and
"futils.c", respectively, but in fact they live in "fileops.h".

Rename the files to match expectations.
configuration: cvar -> configmap 2019-07-18T11:53:41+00:00 Patrick Steinhardt ps@pks.im 2019-07-18T11:53:41+00:00 658022c41affc7d9b5bd9b84b1d75ec909b820c6 `cvar` is an unhelpful name. Refactor its usage to `configmap` for more clarity. 
`cvar` is an unhelpful name.  Refactor its usage to `configmap` for more
clarity.
oid: `is_zero` instead of `iszero` 2019-06-15T23:16:47+00:00 Edward Thomson ethomson@edwardthomson.com 2019-06-08T22:28:35+00:00 5d92e54745eaad2c89aa6457d504411ceee3a4f4 The only function that is named `issomething` (without underscore) was `git_oid_iszero`. Rename it to `git_oid_is_zero` for consistency with the rest of the library. 
The only function that is named `issomething` (without underscore) was
`git_oid_iszero`.  Rename it to `git_oid_is_zero` for consistency with
the rest of the library.
Rename opt init functions to `options_init` 2019-06-14T08:57:00+00:00 Edward Thomson ethomson@edwardthomson.com 2019-06-06T20:36:23+00:00 0b5ba0d744e69da5dc8c08d167c83dd87ed83af2 In libgit2 nomenclature, when we need to verb a direct object, we name a function `git_directobject_verb`. Thus, if we need to init an options structure named `git_foo_options`, then the name of the function that does that should be `git_foo_options_init`. The previous names of `git_foo_init_options` is close - it _sounds_ as if it's initializing the options of a `foo`, but in fact `git_foo_options` is its own noun that should be respected. Deprecate the old names; they'll now call directly to the new ones. 
In libgit2 nomenclature, when we need to verb a direct object, we name
a function `git_directobject_verb`.  Thus, if we need to init an options
structure named `git_foo_options`, then the name of the function that
does that should be `git_foo_options_init`.

The previous names of `git_foo_init_options` is close - it _sounds_ as
if it's initializing the options of a `foo`, but in fact
`git_foo_options` is its own noun that should be respected.

Deprecate the old names; they'll now call directly to the new ones.
patch_parse.c: Handle CRLF in parse_header_start 2019-04-06T00:44:10+00:00 Drew DeVault sir@cmpwn.com 2019-03-23T03:56:10+00:00 30c06b601eaf9b87975a3731ad1051d74b1ae73d 






tests: diff: test parsing diffs with a new file with spaces in its path
2019-03-29T11:51:49+00:00

Erik Aigner
aigner.erik@gmail.com

2019-03-29T11:30:37+00:00

9d65360b4eaa402c8f137684577d0131a861ce8b

Add a test that verifies that we are able to parse patches which add a
new file that has spaces in its path.





Add a test that verifies that we are able to parse patches which add a
new file that has spaces in its path.







git_error: use new names in internal APIs and usage
2019-01-22T22:30:35+00:00

Edward Thomson
ethomson@edwardthomson.com

2018-12-27T19:47:34+00:00

f673e232afe22eb865cdc915e55a2df6493f0fbb

Move to the `git_error` name in the internal API for error-related
functions.





Move to the `git_error` name in the internal API for error-related
functions.