| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
| |
OpenSSL and often whatever libssh2 is using require their own set-up for
concurrent operations to be safe. This means that by default, using both
of these libraries in a threaded context is unsafe.
Lock by default, and allow the user to tell us that they've set up
threading for the underlying libraries.
|
| |\
| |
| | |
openssl: don't try to handle WANT_READ or WANT_WRITE
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
We use a blocking socket and set the mode to AUTO_RETRY which means that
`SSL_write` and `SSL_read` will only return once the read or write has
been completed. We therefore don't need to handle partial writes or
re-try read due to a regenotiation.
While here, consider that a zero also indicates an error condition.
|
| | | |
|
| |\ \ |
|
| | | | |
|
| |\ \ \
| | | |
| | | | |
Fix error when building as C++.
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | | |
index_add_all: include untracked files in new subdirs
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
No need to get reports about individual ignored files, having a
single ignored directory delta is enough.
|
| | |/ / / |
|
| |\ \ \ \
| |/ / /
|/| | | |
ignore: clear the error when matching a pattern negation
|
| |/ / /
| | |
| | |
| | |
| | |
| | | |
When we discover that we want to keep a negative rule, make sure to
clear the error variable, as it we otherwise return whatever was left by
the previous loop iteration.
|
| | | |
| | |
| | |
| | |
| | | |
Our doc parser really wants the types to be declared in the header it's
reading.
|
| |\ \ \
| |/ /
|/| | |
Improve server error reporting
|
| | | |
| | |
| | |
| | |
| | |
| | | |
This can be used by tools to show mesages about failing to communicate
with the server. The error message in this case will often contain the
server's error message, as far as it managed to send anything.
|
| |/ /
| |
| |
| |
| |
| |
| |
| | |
When we fail to read from stdout, it's typically because the URL was
wrong and the server process has sent some output over its stderr
output.
Read that output and set the error message to whatever we read from it.
|
| |\ \
| | |
| | | |
Use a diff for iteration in index_update_all and index_add_all
|
| | | | |
|
| | | |
| | |
| | |
| | | |
Without this option, we would not be able to catch exec bit changes.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
Instead of going through each entry we have and re-adding, which may not
even be correct for certain crlf options and has bad performance, use
the function which performs a diff against the worktree and try to add
and remove files from that list.
|
| | | |
| | |
| | |
| | |
| | | |
Refactor so we look like the code we're replacing, which should also
allow us to more easily inplement add-all.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We currently iterate over all the entries and re-add them to the
index. While this provides correctness, it is wasteful as we try to
re-insert files which have not changed.
Instead, take a diff between the index and the worktree and only re-add
those which we already know have changed.
|
| |\ \ \
| | | |
| | | | |
Provide error messages for git_path_direach operations
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
We set an error if we get an error when reading, but we don't bother
setting an error message for write failing. This causes a cryptic error
to be shown to the user when the target filesystem is full.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Now that `git_path_direach` lets us specify an error message to report,
set an appropriate error message while linking.
|
| |/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This function deals with functions doing IO which means the amount of
errors that can happen is quit large. It does not help if it always
ovewrites the underlying error message with a less understandable
version of "something went wrong".
Instead, only use this generic message if there was no error set by the
callback.
|
| |\ \ \
| | | |
| | | | |
Updated dlibgit link.
|
| | | | | |
|
| |\ \ \ \
| |/ / /
|/| | | |
Bring Early EOF message in line with the other two
|
| |/ / / |
|
| | | | |
|
| |\ \ \
| |/ /
|/| | |
Add tests for and fix push negotiation notification
|
| | | |
| | |
| | |
| | |
| | | |
There was a copypasta error and the source and destination IDs were
reversed.
|
| |/ /
| |
| |
| |
| | |
The functionality was meged without including tests, so let's add them
now.
|
| | | |
|
| |\ \
| | |
| | | |
Attributes: don't match files for folders
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When handling attr matching, simply compare the directory path where the
attribute file resides to the path being matched. Skip over commonality
to allow us to compare the contents of the attribute file to the remainder
of the path.
This allows us to more easily compare the pattern directly to the path,
instead of trying to guess whether we want to compare the path's basename
or the full path based on whether the match was inside a containing
directory or not.
This also allows us to do fewer translations on the pattern (trying to
re-prefix it.)
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When determining whether some file matches an attr pattern, do
not try to truncate the path to pass to fnmatch. When there is
no containing directory for an item (eg, from a .gitignore in the
root) this will cause us to truncate our path, which means that
we cannot do meaningful comparisons on it and we may have false
positives when trying to determine whether a given file is actually
a file or a folder (as we have lost the path's base information.)
This mangling was to allow fnmatch to compare a directory on disk to
the name of a directory, but it is unnecessary as our fnmatch accepts
FNM_LEADING_DIR.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
When ignoring a path "foo/", ensure that this is actually a directory,
and not simply a file named "foo".
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
When a .gitignore specifies some folder "foo/", ensure that a file
with the same name "foo" is not ignored.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Ensure that when examining a .gitignore in a subdirectory, we do not
erroneously apply the paths contained therein to the root of the
repository. (Fixed in c02a0e4).
|
| |\ \ \
| | | |
| | | | |
Use the packbuilder in local push
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
A couple of tests use the wrong remote to push to. We did not notice up
to now because the local push would copy individual objects, and those
already existed, so it became a no-op.
Once we made local push create the packfile, it became noticeable that
there was a new packfile where it didn't belong.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Instead of copying each object individually, as we'd been doing, use the
packbuilder which should be faster and give us some feedback.
While performing this change, we can hook up the packbuilder's writing
to the push progress so the caller knows how far along we are.
|
| | | | | |
|
