| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Check rebase options version on public entry pointsjamill/rebase_opt_ver_check | Jameson Miller | 2015-02-12 | 1 | -1/+3 |
| | | |||||
| * | Check the result of git_buf_joinpath | Jacques Germishuys | 2014-12-30 | 1 | -1/+2 |
| | | |||||
| * | Plug some leaks | Jacques Germishuys | 2014-12-29 | 1 | -1/+2 |
| | | |||||
| * | notes: move the notes name argument | Carlos MartÃn Nieto | 2014-12-06 | 1 | -2/+2 |
| | | | | | | Make it consistent between git_note_create() and git_note_remote() by putting it after the repository. | ||||
| * | rebase: updates based on PR comments | Edward Thomson | 2014-10-26 | 1 | -17/+31 |
| | | |||||
| * | s/git_merge_head/git_annotated_commit | Edward Thomson | 2014-10-26 | 1 | -19/+21 |
| | | | | | | Rename git_merge_head to git_annotated_commit, as it becomes used in more operations than just merge. | ||||
| * | rebase: clean up some warnings and memory leaks | Edward Thomson | 2014-10-26 | 1 | -26/+14 |
| | | |||||
| * | rebase: oid member of operation should be const | Edward Thomson | 2014-10-26 | 1 | -2/+2 |
| | | |||||
| * | git_rebase: iterators for operations | Edward Thomson | 2014-10-26 | 1 | -0/+21 |
| | | |||||
| * | rebase: preload all operations | Edward Thomson | 2014-10-26 | 1 | -111/+151 |
| | | |||||
| * | rebase: init/open a git_rebase object | Edward Thomson | 2014-10-26 | 1 | -234/+276 |
| | | |||||
| * | git_rebase_next: provide info about the operation | Edward Thomson | 2014-10-26 | 1 | -2/+9 |
| | | |||||
| * | git_rebase_finish: rewrite notes when finishing rebase | Edward Thomson | 2014-10-26 | 1 | -16/+150 |
| | | |||||
| * | git_rebase_commit: write HEAD's reflog appropriately | Edward Thomson | 2014-10-26 | 1 | -3/+9 |
| | | |||||
| * | Introduce git_rebase_finish to complete a rebase | Edward Thomson | 2014-10-26 | 1 | -1/+62 |
| | | |||||
| * | git_rebase_commit: drop already-picked commits | Edward Thomson | 2014-10-26 | 1 | -4/+15 |
| | | | | | | | 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. | ||||
| * | Introduce git_rebase_commit | Edward Thomson | 2014-10-26 | 1 | -11/+110 |
| | | | | | Commit the current patch of a rebase process. | ||||
| * | git_rebase_next: write conflicts nicely during rebase | Edward Thomson | 2014-10-26 | 1 | -18/+102 |
| | | |||||
| * | Introduce git_rebase_next | Edward Thomson | 2014-10-26 | 1 | -0/+156 |
| | | | | | | | `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. | ||||
| * | Introduce git_rebase_abort | Edward Thomson | 2014-10-26 | 1 | -0/+128 |
| | | | | | | 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 | Edward Thomson | 2014-10-26 | 1 | -0/+332 |
| Introduce `git_rebase` to set up a rebase session that can then be continued. Immediately, only merge-type rebase is supported. | |||||
 |
index : delta/libgit2.git | |
| github.com: libgit2/libgit2.git |
| summaryrefslogtreecommitdiff |