| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|/ / |
|
|\ \
| |/
|/| |
peel: reject bad queries with EPEEL
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
There are some combination of objects and target types which we know
cannot be fulfilled. Return EINVALIDSPEC for those to signify that there
is a mismatch in the user-provided data and what the object model is
capable of satisfying.
If we start at a tag and in the course of peeling find out that we
cannot reach a particular type, we return EPEEL.
|
| |
| |
| |
| |
| | |
On disconnect we simply ask the transport to close the connection, we do
not free it.
|
|/
|
|
|
| |
Make it clear that this is not the ls-remote command but a way to access
the data we have and how long it's kept around.
|
|\
| |
| | |
Provide a convenience function `git_remote_push()`
|
| |
| |
| |
| |
| | |
If the user does not pass any refspecs to push, try to use those
configured via the configuration or via add_push().
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This function, similar in style to git_remote_fetch(), performs all the
steps required for a push, with a similar interface.
The remote callbacks struct has learnt about the push callbacks, letting
us set the callbacks a single time instead of setting some in the remote
and some in the push operation.
|
|/
|
|
|
|
| |
This describes their purpose better, as we now initialize ssl and some
other global stuff in there. Calling the init function is not something
which has been optional for a while now.
|
|\
| |
| | |
Refactor fetchhead
|
| |
| |
| |
| | |
This gets the value from branch.<foo>.remote.
|
|\ \
| | |
| | | |
remote: rename _load() to _lookup()
|
| |/
| |
| |
| | |
This brings it in line with the rest of the lookup functions.
|
|/
|
|
|
|
| |
This function has one output but can match multiple files, which can be
unexpected for the user, which would usually path the exact path of the
file he wants the status of.
|
|\
| |
| | |
Threading and crypto libraries
|
| |
| |
| |
| |
| | |
Extract the lock-setting functions into their own, as we cannot assume
that it's ok for us to set this unconditionally.
|
|\ \
| | |
| | | |
Changed context_lines and interhunk_lines to uint32_t to match struct s_xdemitconf
|
| |/
| |
| |
| | |
s_xdemitconf
|
|/
|
|
|
| |
Since it's not necessarily obvious, mention the merging state and how to
clear it.
|
| |
|
|
|
|
|
| |
Rename git_merge_head to git_annotated_commit, as it becomes used
in more operations than just merge.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Already cherry-picked commits should not be re-included. If all changes
included in a commit exist in the upstream, then we should error with
GIT_EAPPLIED.
|
|
|
|
| |
Commit the current patch of a rebase process.
|
|
|
|
|
|
| |
`git_rebase_next` will apply the next patch (or cherry-pick)
operation, leaving the results checked out in the index / working
directory so that consumers can resolve any conflicts, as appropriate.
|
|
|
|
|
| |
Abort an in-progress rebase and move the working directory and
repository back to the ORIG_HEAD state.
|
| |
|
|
|
|
|
|
| |
Introduce `git_rebase` to set up a rebase session that can
then be continued. Immediately, only merge-type rebase is
supported.
|
|\
| |
| | |
config: remove the refresh function and backend field
|
| |
| |
| |
| |
| |
| | |
We have been refreshing on read and write for a while now, so
git_config_refresh() is at best a no-op, and might just end up wasting
cycles.
|
|\ \
| | |
| | | |
remote: accept a repo and name for renaming
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Remote objects are not meant to be changed from under the user. We did
this in rename, but only the name and left the refspecs, such that a
save would save the wrong refspecs (and a fetch and anything else would
use the wrong refspecs).
Instead, let's simply take a name and not change any loaded remote from
under the user.
|
|/
|
|
|
|
|
| |
This function does not in fact tell us anything, as almost anything with
a colon in it is a valid rsync-style SSH path; it can not tell us that
we do not support ftp or afp or similar as those are still valid SSH
paths and we do support that.
|
| |
|
|
|
|
| |
FLAG_BITS only seems to be used internally
|
|\
| |
| | |
remote: accept a repository and remote name for deletion
|
| |
| |
| |
| |
| |
| |
| |
| | |
We don't need the remote loaded, and the function extracted both of
these from the git_remote in order to do its work, so let's remote a
step and not ask for the loaded remote at all.
This fixes #2390.
|
|\ \
| | |
| | | |
[factor] Join typedef and struct definitions in single file.
|
| | | |
|
|\ \ \
| | | |
| | | | |
Add support for setting the SSL CA location
|
| | |/
| |/|
| | |
| | |
| | | |
This allows users to specify self-signed certificates, or to provide their
own certificate stores on limited platforms such as mobile phones.
|
|\ \ \
| | | |
| | | | |
Allow to propagate checkout callbacks to git HARD reset
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Sven Strickroth <email@cs-ware.de>
|