| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | |
| | | |
| | | |
| | | | |
It calls git_mempack_reset which reallocates the object array. git_oidmap_free is now called on it explicitly.
|
|/ / /
| | |
| | |
| | | |
git_mempack_reset was leaving free'd pointers in the oidmap.
|
|\ \ \
| | | |
| | | | |
report libssh2 error if list of authentication methods can't be retrieved
|
| | | |
| | | |
| | | |
| | | | |
to retrieve the list of authentication methods
|
|\ \ \ \
| | | | |
| | | | | |
index: canonicalize directory case when adding
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
On case insensitive platforms, allow `git_index_add` to provide a new
path for an existing index entry. Previously, we would maintain the
case in an index entry without the ability to change it (except by
removing an entry and re-adding it.)
Higher-level functions (like `git_index_add_bypath` and
`git_index_add_frombuffers`) continue to keep the old path for easier
usage.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
On case insensitive systems, when given a user-provided path in the
higher-level index addition functions (eg `git_index_add_bypath` /
`git_index_add_frombuffer`), examine the index to try to match the
given path to an existing directory.
Various mechanisms can cause the on-disk representation of a folder
to not match the representation in HEAD or the index - for example,
a case changing rename of some file `a/file.txt` to `A/file.txt`
will update the paths in the index, but not rename the folder on
disk.
If a user subsequently adds `a/other.txt`, then this should be stored
in the index as `A/other.txt`.
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
New feature: add the ablility to iterate through a directory in index
|
| | |_|/
| |/| |
| | | |
| | | | |
Find the first index entry matching a prefix.
|
|\ \ \ \
| | | | |
| | | | | |
filebuf: follow symlinks when creating a lock file
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
We create a lockfile to update files under GIT_DIR. Sometimes these
files are actually located elsewhere and a symlink takes their place. In
that case we should lock and update the file at its final location
rather than overwrite the symlink.
|
|\ \ \ \
| |/ / /
|/| | | |
Use a hashmap for path-based lookups in the index
|
| | | |
| | | |
| | | |
| | | |
| | | | |
This should let us see more clearly what we're doing and avoid the ugly
'if' we need every time we want to interact with the map.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
The hash table allows quick lookup of specific paths, while we use the
vector for enumeration.
|
| | | |
| | | |
| | | |
| | | | |
They are hashed case-insensitively and take the stage into account.
|
|\ \ \ \
| | | | |
| | | | | |
Provide path matching in the iterators (for faster diffs)
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Some nicer refactoring for index iteration walks.
The index iterator doesn't binary search through the pathlist space,
since it lacks directory entries, and would have to binary search
each index entry and all its parents (eg, when presented with an index
entry of `foo/bar/file.c`, you would have to look in the pathlist for
`foo/bar/file.c`, `foo/bar` and `foo`). Since the index entries and the
pathlist are both nicely sorted, we walk the index entries in lockstep
with the pathlist like we do for other iteration/diff/merge walks.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Now that non-pathspec matching diffs are implemented at the iterator
level, drop `FILELIST_MATCH`ing.
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
When using literal pathspecs in diff with `GIT_DIFF_DISABLE_PATHSPEC_MATCH`
turn on the faster iterator pathlist handling.
Updates iterator pathspecs to include directory prefixes (eg, `foo/`)
for compatibility with `GIT_DIFF_DISABLE_PATHSPEC_MATCH`.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
When given a pathlist, don't assume that directories sort before
files. Walk through any list of entries sorting before us to make
sure that we've exhausted all entries that *aren't* directories.
Eg, if we're searching for 'foo/bar', and we have a 'foo.c', keep
advancing the pathlist to keep looking for an entry prefixed with
'foo/'.
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
win32: ensure hidden files can be staged
|
| | | | | |
|
|\ \ \ \ \
| |_|_|_|/
|/| | | | |
Include the 4 characters not recognised as hex-number in parse_len
|
| | | | |
| | | | |
| | | | |
| | | | | |
parse_len
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
libgit2 implementations of smart subtransports can simply reach through
the structure, but external implementors cannot.
Add these two functions as a way for the smart subtransports to get the
callbacks as set by the user.
|
| | | | |
| | | | |
| | | | |
| | | | | |
‘git_transaction_config_new’
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Fix bug in git_smart__push: push_transfer_progress cb is only called at end
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The conditional checked cbs->transfer_progress then used the value in cbs->push_transfer_progress. In both cases it should be push_transfer_progress
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
diff: don't error out on an invalid regex
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
When parsing user-provided regex patterns for functions, we must not
fail to provide a diff just because a pattern is not well
formed. Ignore it instead.
|
|/ / / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
When we ask for credentials, the user may choose to return EUSER to
indicate that an error has happened on its end and it wants to be given
back control.
We must therefore pass that back to the user instead of mentioning that
it was on_headers_complete() that returned an error code. Since we can,
we return the exact error code from the user (other than PASSTHROUGH)
since it doesn't cost anything, though using other error codes aren't
recommended.
|
|\ \ \ \ \ \
| |_|_|_|_|/
|/| | | | | |
curl: use the most secure auth method for the proxy
|
| | |_|_|/
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
When curl uses a proxy, it will only use Basic unless we prompt it to
try to use the most secure on it has available.
This is something which git did recently, and it seems like a good idea.
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Locking and transactional/atomic updates for config
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This makes the API for commiting or discarding changes the same as for
references.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This lock/unlock pair allows for the cller to lock a configuration file
to avoid concurrent operations.
It also allows for a transactional approach to updating a configuration
file. If multiple updates must be made atomically, they can be done
while the config is locked.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
When a configuration file is locked, any updates made to it will be done
to the in-memory copy of the file. This allows for multiple updates to
happen while we hold the lock, preventing races during complex
config-file manipulation.
|
| |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Instead of writing into the filebuf directly, make the functions to
write the modified config file write into a buffer which can then be
dumped into the lockfile for committing.
This allows us to re-use the same code for modifying a locked
configuration, as we can simply skip the last step of dumping the data
to disk.
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | | |
When we're looking to update a tag, we can't stop if the tag auto-follow
rules don't say to update it. The tag might still match the refspec we
were given.
|
| |/ /
|/| |
| | |
| | |
| | |
| | |
| | | |
With Visual Studio versions 2008 and older they ignore the full path to files and only check
the basename of the file to find a collision. Additionally, having duplicate basenames can break
other build tools like GYP.
This fixes https://github.com/libgit2/libgit2/issues/3356
|
| | |
| | |
| | |
| | |
| | | |
When an error state is an OOM, make sure that we treat is specially
and do not try to free it.
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Instead of allocating a brand new buffer for each error string we want
to store, we can use a per-thread buffer to store the error string and
re-use the underlying storage. We already use the buffer to format the
string, so this mostly makes that more direct.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Allow restoring a previously captured oom error, by
detecting when the captured message pointer points to the
static oom error message. This means there is no need
to strdup the message in giterr_detach.
|