| Commit message (Collapse) | Author | Age | Files | Lines |
| |\
| |
| | |
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>
|
| |\ \ \ \
| | | | |
| | | | | |
Provide host name to certificate_check_cb
|
| | | |/ /
| |/| |
| | | |
| | | | |
Signed-off-by: Sven Strickroth <email@cs-ware.de>
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | | |
Implement git-describe
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
And implement the option init functions for this and the format options.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
When we describe the workdir, we perform a describe on HEAD and then
check to see if the worktree is dirty. If it is and we have a suffix
string, we append that to the buffer.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Instead of printing out to the buffer inside the information-gathering
phase, write the data to a intermediate result structure.
This allows us to split the options into gathering options and
formatting options, simplifying the gathering code.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
We don't describe arbitrary object, so let's give it the name of the one
object type we accept.
|
| | |\ \ \ \
| | |/ / / |
|
| | | | | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
Introduce reference transactions
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This leaves space for future expansion to locking other resources
without having to change the API for references.
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
A transaction allows you to lock multiple references and set up changes
for them before applying the changes all at once (or as close as the
backend supports).
This can be used for replication purposes, or for making sure some
operations run when the reference is locked and thus cannot be changed.
|
| | | |/ / /
| |/| | | |
|