| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | |
| | |
| | |
| | |
| | | |
This allows you to set up the repository and remote as you which to
have them before performing the clone operation.
|
| | |
| | |
| | |
| | |
| | | |
Move this one as well, letting us have a single way of setting the
callbacks for the remote, and removing fields from the clone options.
|
| |/
|/|
| |
| |
| |
| | |
The text progress and update_tips callbacks are already part of the
struct, which was meant to unify the callback setup, but the download
one was left out.
|
| | |
|
| | |
|
|\ \
| | |
| | | |
Config subsection name should allow to have ']' and '\\' should allow to escape any characters
|
| | |
| | |
| | |
| | | |
escape any characters
|
|\ \ \
| | | |
| | | | |
Redir refactor
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
...and have that call manage replaced memory in the output structure.
|
| | | | |
|
| | | | |
|
| |/ / |
|
|\ \ \
| | | |
| | | | |
Initial Implementation of progress reports during push
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This adds the basics of progress reporting during push. While progress
for all aspects of a push operation are not reported with this change,
it lays the foundation to add these later. Push progress reporting
can be improved in the future - and consumers of the API should
just get more accurate information at that point.
The main areas where this is lacking are:
1) packbuilding progress: does not report progress during deltafication,
as this involves coordinating progress from multiple threads.
2) network progress: reports progress as objects and bytes are going
to be written to the subtransport (instead of as client gets
confirmation that they have been received by the server) and leaves
out some of the bytes that are transfered as part of the push protocol.
Basically, this reports the pack bytes that are written to the
subtransport. It does not report the bytes sent on the wire that
are received by the server. This should be a good estimate of
progress (and an improvement over no progress).
|
|\ \ \ \
| | | | |
| | | | | |
Never consider submodules for stashing
|
| | |/ /
| |/| | |
|
|\ \ \ \
| |_|/ /
|/| | | |
Fix x86/x64 size_t related warnings
|
| |/ / |
|
|/ /
| |
| |
| | |
Fix libgit2/libgit2sharp#522
|
| | |
|
| | |
|
|\ \
| | |
| | | |
Alternative fix for cross protocol redirects
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The subtransport path was relying on pointing to data owned by
the remote which meant that after a redirect, the updated path
was getting lost for future requests. This updates the http
transport to strdup the path and maintain its own lifetime.
This also pulls responsibility for parsing the URL back into the
http transport and isolates the functions that parse and free that
connection data so that they can be reused between the initial
parsing and the redirect parsing.
|
| | | |
|
| | | |
|
|/ /
| |
| |
| |
| |
| | |
On occasion, files can disappear while we're iterating the
filesystem, between calls to readdir and stat. Let's pretend
those didn't exist in the first place.
|
|\ \
| | |
| | | |
Various warning cleanup and minor fixes
|
| | |
| | |
| | |
| | |
| | |
| | | |
The git_buf_text_gather_stats call returns a boolean indicating if
the file looks like binary data. That shouldn't be an error; it
should be used to skip CRLF processing though.
|
| | |
| | |
| | |
| | |
| | |
| | | |
This replaces some git_buf_printf calls with simple calls to
git_buf_put instead. Also, it fixes a missing va_end inside
the git_buf_vprintf implementation.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The attempt to "clean up warnings" seems to have introduced some
new warnings on compliant compilers. This fixes those in a way
that I suspect will also be okay for the non-compliant compilers.
Also this fixes what appears to be an extra semicolon in the
repo initialization template dir handling (and as part of that
fix, handles the case where an error occurs correctly).
|
|\ \ \
| | | |
| | | | |
Minimize regex usage
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In revwalk, we are doing a very simple check to see if a string
contains wildcard characters, so a full regular expression match
is not needed.
In remote listing, now that we have git_config_foreach_match with
full regular expression matching, we can take advantage of that
and eliminate the regex here, replacing it with much simpler string
manipulation.
|
|/ / |
|
|\ \
| | |
| | | |
Fix typo in documentation
|
| | | |
|
|/ /
| |
| |
| | |
Make it pair up with the one for commits. This fixes #1691.
|
|\ \
| | |
| | | |
Fix warning
|
| | | |
|
|\ \ \
| | | |
| | | | |
Make init.templatedir work
|
| | | | |
|
| | | | |
|
| | | | |
|
|\ \ \ \
| |/ / /
|/| | | |
indexer: check the packfile trailer
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
The packfile trailer gets sent over and we should check whether it's
correct as part of our sanity checks of the packfile.
|