| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
git_remote_set_transport now takes a transport factory rather than a transport
git_clone_options now allows the caller to specify a remote creation callback
|
| |
|
|
|
|
| |
This was a bad idea. Don't free except in the free function.
|
|
|
|
|
|
| |
There is no reason why we need to use a callback here. A string array
fits better with the usage, as this is not an event and we don't need
anything from the user.
|
|
|
|
|
| |
If the remote supports the symref protocol extension, then we return
that, otherwise we guess with git's rules.
|
|\
| |
| | |
Remote deletion
|
| | |
|
|/
|
|
|
| |
There were a couple of "init_opts()" functions a few more cases
of structure initialization that I somehow missed.
|
|\
| |
| | |
Fire progress and update tips callbacks also for pushes.
|
| | |
|
| | |
|
| |
| |
| |
| | |
The user may have requested that the operation be cancelled.
|
| |
| |
| |
| |
| | |
It's not very useful to only know that a pre-receive hook has declined
a push, you probably want to know why.
|
| |
| |
| |
| |
| |
| |
| |
| | |
Allow the credentials callback to return GIT_PASSTHROUGH to make the
transports code behave as though none was set.
This should make it easier for bindings to behave closer to the C code
when there is no credentials callback set at their level.
|
|/
|
|
|
| |
This should make it easier for bindings to dynamically override their
own callbacks.
|
|
|
|
|
|
|
|
|
|
| |
The order in this function is the opposite to what
create_with_fetchspec() has, so change this one, as url-then-refspec is
what git does.
As we need to break compilation and the swap doesn't do that, let's take
this opportunity to rename in-memory remotes to anonymous as that's
really what sets them apart.
|
|
|
|
| |
The basic structure of each function is courtesy of arrbee.
|
| |
|
| |
|
|
|
| |
Also added a test for git_remote_fetch.
|
| |
|
| |
|
| |
|
|\
| |
| | |
Allowing create remotes with custom fetch spec
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The callback-based method of listing remote references dates back to the
beginning of the network code's lifetime, when we didn't know any
better.
We need to keep the list around for update_tips() after disconnect() so
let's make use of this to simply give the user a pointer to the array so
they can write straightforward code instead of having to go through a
callback.
|
| |
| |
| |
| |
| |
| | |
Removing arbitrary refspecs makes things more complex to reason
about. Instead, let the user set the fetch and push refspec list to
whatever they want it to be.
|
|/
|
|
|
|
|
| |
The correct behaviour when a remote has no refspecs (e.g. a URL from the
command-line) is to download the remote's HEAD. Let's do that.
This fixes #1261.
|
| |
|
|
|
|
|
| |
There are any number of issues that can come up in the progress
callback, and we should let the user cancel at that point as well.
|
|
|
|
| |
There's no need for this to be a pointer to somewhere else.
|
|
|
|
| |
Hopefully clear up what they're for.
|
| |
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
| |
The description of what the function does hasn't been true for quite a
while. Change it to reflect the way it currently works.
While here, remove an even older comment about missing features that
have been implemented.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Fixed a few header @param and @return typos with the help of -Wdocumentation in Xcode.
The following warnings have not been fixed:
common.h:213 - Not sure how the documentation format is for '...'
notes.h:102 - Correct @param name but empty text
notes.h:111 - Correct @param name but empty text
pack.h:140 - @return missing text
pack.h:148 - @return missing text
|
| |
|
|
|
|
|
|
| |
Bring back a way of acessing the git_refspec* from a remote.
Closes #1514
|
| |
|
|
|
|
|
|
|
|
| |
Introduce git_remote_{fetch,push}_refspecs() to get a list of refspecs
from the remote and rename the refspec-adding functions to a less
silly name.
Use this instead of the vector index hacks in the tests.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A remote can have a multitude of refspecs. Up to now our git_remote's
have supported a single one for each fetch and push out of simplicity
to get something working.
Let the remotes and internal code know about multiple remotes and get
the tests passing with them.
Instead of setting a refspec, the external users can clear all and add
refspecs. This should be enough for most uses, though we're still
missing a querying function.
|
|
|
|
| |
This fixes #1487
|
|
|
|
| |
Fix libgit2/libgit2sharp#318
|
|
|
| |
Fixes #1232
|
| |
|