| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|\
| |
| | |
filters: custom filters with wildcard attributes
|
| |
| |
| |
| |
| |
| | |
Allow custom filters with wildcard attributes, so that clients
can support some random `filter=foo` in a .gitattributes and look
up the corresponding smudge/clean commands in the configuration file.
|
|\ \
| | |
| | | |
git__getenv: utf-8 aware env reader
|
| | |
| | |
| | |
| | |
| | |
| | | |
Introduce `git__getenv` which is a UTF-8 aware `getenv` everywhere.
Make `cl_getenv` use this to keep consistent memory handling around
return values (free everywhere, as opposed to only some platforms).
|
|/ /
| |
| |
| |
| |
| | |
Don't use the filter's free callback to free the actual data structure
holding the filter, as we may not always actually initialize it (the
test may be skipped).
|
|/ |
|
|
|
|
|
| |
All platforms do terrible, horrible, no good, very bad translation
when core.autocrlf=true. It's not just Windows!
|
|
|
|
|
| |
`git_filter_list_contains` can be used to query a filter list to
determine if a given filter will be run.
|
|
|
|
|
| |
Git inserts a space after the SHA1 (as of 2.1.4 at least), so do the
same.
|
| |
|
|
|
|
|
| |
Test that filter_list_apply_to_file works and can accept repo-relative
paths.
|
|
|
|
|
|
| |
Introduce GITTEST_INVASIVE_FS_STRUCTURE for things that are invasive
to your filesystem structure (like creating folders at your filesystem
root) and GITTEST_INVASIVE_FS_SIZE for things that write lots of data.
|
|
|
|
|
| |
For consistency with the rest of the library, where an opt is an
options *structure*.
|
| |
|
| |
|
|
|
|
|
| |
Test pushing a file on-disk into a streaming filter that compresses
it into the ODB, and inflates it back into the working directory.
|
| |
|
| |
|
|
|
|
|
|
| |
If you enabled core.safecrlf on an LF-ending platform, we would
error even for files with all LFs. We should only be warning on
irreversible mappings, I think.
|
|
|
|
|
|
|
|
|
| |
Diff and status do not want core.safecrlf to actually raise an
error regardless of the setting, so this extends the filter API
with an additional options flags parameter and adds a flag so that
filters can be applied with GIT_FILTER_OPT_ALLOW_UNSAFE, indicating
that unsafe filter application should be downgraded from a failure
to a warning.
|
| |
|
| |
|
|
|
|
| |
This was not converted when we converted the rest, so do it now.
|
| |
|
|
|