| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |\
| |
| | |
Allowing create remotes with custom fetch spec
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
ld was warning that the size of path changed, rightly so.
|
| |\ \
| | |
| | | |
Remote revamp (director's cut)
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| | | |
|
| | | |
|
| | | |
|
| |/ |
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
At some moment git_config_delete_entry lost the ability to delete one entry of
a multivar configuration. The moment you had more than one fetch or push
ref spec for a remote you will not be able to save that remote anymore. The
changes in network::remote::remotes::save show that problem.
I needed to create a new git_config_delete_multivar because I was not able to
remove one or several entries of a multivar config with the current API.
Several tries modifying how git_config_set_multivar(..., NULL) behaved were
not successful.
git_config_delete_multivar is very similar to git_config_set_multivar, and
delegates into config_delete_multivar of config_file. This function search
for the cvar_t that will be deleted, storing them in a temporal array, and
rebuilding the linked list. After calling config_write to delete the entries,
the cvar_t stored in the temporal array are freed.
There is a little fix in config_write, it avoids an infinite loop when using
a regular expression (case for the multivars). This error was found by the
test network::remote::remotes::tagopt.
|
| |/ |
|
| | |
|
| |
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
| |
...and have that call manage replaced memory in the output structure.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
In order to be loaded, a remote needs to be configured with at least a `url` or a `pushurl`.
ENOTFOUND will be returned when trying to git_remote_load() a remote with neither of these entries defined.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Accept any value for the remote's url, including an empty string which
we used to reject as invalid configuration.
This is not quite what git does (although it has its own problems with
such configurations) and it makes it harder to fix the issue, by not
letting the user modify it.
As we already need to check for a valid URL when we try to connect to
the network, let that perform the check, as we don't need to do it
anywhere else.
|
| | |
|
| |
|
|
|
| |
Default for newly created remotes will be auto.
Default when loading existing remotes with no tag retrieving behaviour set, was already auto.
|
| | |
|
| |\
| |
| | |
Introduce a refs iterator
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Nobody should ever be using anything other than ALL at this level, so
remove the option altogether.
As part of this, git_reference_foreach_glob is now implemented in the
frontend using an iterator. Backends will later regain the ability of
doing the glob filtering in the backend.
|
| |\ \
| | |
| | | |
Fix windows diff eofnl error
|
| | |/ |
|
| |/
|
|
|
|
|
| |
When tagopt is set to '--tags', we should only take the default tags
refspec into account and ignore any configured ones.
Bring the code into compliance.
|
| |
|
|
|
|
| |
Bring back a way of acessing the git_refspec* from a remote.
Closes #1514
|
| |
|
|
|
| |
As git allows you to store shorthand refspecs in the configuration, we
need to do this ourselves.
|
| |
|
|
|
| |
Relax the ONELEVEL ref naming rules so the refspec parsing code can
ask for 'master' to be considered valid.
|
| |
|
|
|
|
|
|
| |
It used to be separate as an attempt to make the querying easier, but
it didn't work out that way, so put all the data together.
Add git_refspec_string() as well to get the original string, which is
now stored alongside the independent parts.
|
| |
|
|
|
|
|
|
| |
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 makes the size_t comparison test nicer (assuming that the
values are actually not using the full length), and converts
some cases that were using it for pointer comparison to use the
macro that is designed for pointer comparison.
|
| | |
|
| |\
| |
| | |
Allow network operations to cancel
|
| | |
| |
| |
| |
| | |
This works by having the indexer watch the return
code of the callback, so will only take effect
on object boundaries.
|
| | |
| |
| |
| | |
Fix libgit2/libgit2sharp#318
|
| | | |
|
| |/ |
|
| | |
|
| | |
|
