delta/libgit2.git/include/git2/repository.h, branch ethomson/gitstr github.com: libgit2/libgit2.git repository: improve `hashfile` for absolute paths 2021-09-25T13:39:01+00:00 Edward Thomson ethomson@edwardthomson.com 2021-09-24T19:23:34+00:00 0f4256b8d78cf602192e0546d185953ee1b30fd5 When `git_repository_hashfile` is handed an absolute path, it determines whether the path is within the repository's working directory or not. This is necessary when there is no `as_path` specified. If the path is within the working directory, then the given path should be used for attribute lookups (it is the effective `as_path`). If it is not within the working directory, then it is _not_ eligible. Importantly, now we will _never_ pass an absolute path down to attribute lookup functions. 
When `git_repository_hashfile` is handed an absolute path, it determines
whether the path is within the repository's working directory or not.
This is necessary when there is no `as_path` specified.

If the path is within the working directory, then the given path should
be used for attribute lookups (it is the effective `as_path`).  If it is
not within the working directory, then it is _not_ eligible.

Importantly, now we will _never_ pass an absolute path down to attribute
lookup functions.
Fix coding style for pointer 2021-09-09T17:49:04+00:00 punkymaniac punkymaniac@protonmail.ch 2021-09-09T17:49:04+00:00 379c46463cbdd73e04c5efc180309d4600e56624 Make some syntax change to follow coding style. 
Make some syntax change to follow coding style.
Fix documentation formating on repository.h 2021-02-22T13:58:46+00:00 punkymaniac punkymaniac@protonmail.ch 2021-02-22T13:58:46+00:00 3bb5f29733808f18ffd009529a49ec4e4953a31b The enum 'git_repository_init_flag_t', 'git_repository_init_mode_t' and the structure 'git_repository_init_options' does not follow the format used by docurium. 
The enum 'git_repository_init_flag_t', 'git_repository_init_mode_t' and
the structure 'git_repository_init_options' does not follow the format
used by docurium.
repository: improve commondir docs 2020-03-08T00:05:25+00:00 Josh Bleecher Snyder josharian@gmail.com 2020-03-08T00:04:04+00:00 a5886e9e0e5bcc2b3b42082fa3f443189d3974a3 Fixes #5428 
Fixes #5428
repo: commondir resolution can sometimes fallback to the repodir 2019-06-26T12:49:50+00:00 Etienne Samson samson.etienne@gmail.com 2019-06-26T12:49:50+00:00 501c51b2446b229655638ea6ad003fdc88b77760 For example, https://git-scm.com/docs/gitrepository-layout says: info Additional information about the repository is recorded in this directory. This directory is ignored if $GIT_COMMON_DIR is set and "$GIT_COMMON_DIR/info" will be used instead. So when looking for `info/attributes`, we need to check the commondir first, or fallback to "our" `info/attributes`. 
For example, https://git-scm.com/docs/gitrepository-layout says:

    info
    Additional information about the repository is recorded in this directory.
    This directory is ignored if $GIT_COMMON_DIR is set
    and "$GIT_COMMON_DIR/info" will be used instead.

So when looking for `info/attributes`, we need to check the commondir first,
or fallback to "our" `info/attributes`.
doc: add missing documentation comments 2019-06-15T14:15:50+00:00 Etienne Samson samson.etienne@gmail.com 2019-06-13T18:17:01+00:00 764196fffb76b5ddefb378910877c737778cb500 






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.







repo: split git_repository_open_flag_t options documentation inline
2019-01-28T12:05:52+00:00

Etienne Samson
samson.etienne@gmail.com

2019-01-04T18:09:42+00:00

690e55e00211e7427052518d658200a5f9956240












Introduce GIT_CALLBACK macro to enforce cdecl
2019-01-17T21:17:32+00:00

Edward Thomson
ethomson@edwardthomson.com

2019-01-09T18:25:10+00:00

22d2062d954dcb88fa3dc65281d3f3d88ae87d68

Since we now always build the library with cdecl calling conventions,
our callbacks should be decorated as such so that users will not be able
to provide callbacks defined with other calling conventions.

The `GIT_CALLBACK` macro will inject the `__cdecl` attribute as
appropriate.





Since we now always build the library with cdecl calling conventions,
our callbacks should be decorated as such so that users will not be able
to provide callbacks defined with other calling conventions.

The `GIT_CALLBACK` macro will inject the `__cdecl` attribute as
appropriate.







object_type: update public API to use git_object_t
2018-12-01T10:44:16+00:00

Edward Thomson
ethomson@edwardthomson.com

2018-11-14T23:35:48+00:00

19faf7c5fcd24fab789d9b7a619b343c1fae7c86

git_object_t is the future; update the public API to use it.  This will
also ensure that we can build our tests which make use of the old API
without modification (and without compiler warnings).





git_object_t is the future; update the public API to use it.  This will
also ensure that we can build our tests which make use of the old API
without modification (and without compiler warnings).