| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
| |
Starting at OS X 10.8, the Security framework offers some functions
which are unified across OS X and iOS. These are the functions that we
use.
Older versions of OS X do not have these functions and we fail to
compile. In these situations, fall back to using OpenSSL for our TLS
stream instead.
|
| |\
| |
| | |
Fix build warning: implicit declaration of function ‘git_transaction_config_new’
|
| |/
|
|
| |
‘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.
|
| |\ \ \
| |/ /
|/| | |
http: propagate the credentials callback's error code
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |\ \ \ \
| |/ / /
|/| | | |
remote: don't confuse tag auto-follow rules with refspec matching
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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.
|
| | |/ /
| | |
| | |
| | |
| | |
| | | |
While we download the remote's remote-tracking branches, we don't
download the tag. This points to the tag auto-follow rules interfering
with the refspec.
|
| |\ \ \
| |/ /
|/| | |
Forcing libssh2 lib location in CMake
|
| |/ /
| |
| |
| | |
OS X may have libssh2 in diff locations, so CHECK_LIBRARY_EXISTS may check the wrong lib; forcing it to use a found directory.
|
| |\ \
| | |
| | | |
Fix duplicate basenames to support older VS on master
|
| |/ /
| |
| |
| |
| |
| |
| | |
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
|
| |\ \
| | |
| | | |
Error handling: use buffers, improved OOM handling
|
| | | |
| | |
| | |
| | |
| | | |
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.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Error messages that are detached are assumed to be dynamically
allocated. Passing a pointer to the static oom error message
can cause an attempt to free the static buffer later. This change
checks if the oom error message is about to be detached and detaches
a copy instead.
|
| |/ / / |
|
| |\ \ \
| | | |
| | | | |
filebuf: remove lockfile upon rename errors
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When we have an error renaming the lockfile, we need to make sure
that we remove it upon cleanup. For this, we need to keep track of
whether we opened the file and whether the rename succeeded.
If we did create the lockfile but the rename did not succeed, we
remove the lockfile. This won't protect against all errors, but
the most common ones (target file is open) does get handled.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
When we fail to rename, we currently leave the lockfile laying
around. This shows that behaviour.
|
| |\ \ \ \
| | | | |
| | | | | |
index: stage an unregistered submodule as well
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
We previously added logic to `_add_bypath()` to update a submodule. Go
further and stage the submodule even if it's not registered to behave
like git.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
When we pass the path of a repository to `_bypath()`, we should behave
like git and stage it as a `_COMMIT` regardless of whether it is
registered a a submodule.
|
| | | | | | |
|
| |\ \ \ \ \
| |/ / / /
|/| | | | |
Handle ssh:// and git:// urls containing a '~' character.
|
| |/ / / /
| | | |
| | | |
| | | |
| | | | |
For such a path '/~/...' the leading '/' is stripped so the server will
get a path starting with '~' and correctly handle it.
|
| |\ \ \ \
| | | | |
| | | | | |
Resolve documentation warnings
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | |_|/
| |/| | |
|
| |\ \ \ \
| | | | |
| | | | | |
Remove extra semicolon outside of a function
|
| |/ / / /
| | | |
| | | |
| | | |
| | | | |
Without this change, compiling with gcc and pedantic generates warning:
ISO C does not allow extra ‘;’ outside of a function.
|
| |\ \ \ \
| | | | |
| | | | | |
iterator: skip over errors in diriter init
|
