Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Fix #3094 - improve use of portable size_t/ssize_t format specifiers. | Matthew Plough | 2015-07-12 | 1 | -2/+2 |
| | | | | The header src/cc-compat.h defines portable format specifiers PRIuZ, PRIdZ, and PRIxZ. The original report highlighted the need to use these specifiers in examples/network/fetch.c. For this commit, I checked all C source and header files not in deps/ and transitioned to the appropriate format specifier where appropriate. | ||||
* | Initialize a few variables | Carlos Martín Nieto | 2015-06-09 | 1 | -1/+1 |
| | | | | | | Coverity complains about the git_rawobj ones because we use a loop in which we keep remembering the old version, and we end up copying our object as the base, so we want to have the data pointer be NULL. | ||||
* | rebase: include checkout opts within rebase opts | Edward Thomson | 2015-04-20 | 1 | -14/+6 |
| | |||||
* | rebase: init and open take a rebase_options | Edward Thomson | 2015-04-20 | 1 | -114/+118 |
| | | | | | | `git_rebase_init` and `git_rebase_open` should take a `git_rebase_options` and use it for future rebase operations on that `rebase` object. | ||||
* | rebase: take `checkout_options` where appropriate | Edward Thomson | 2015-04-20 | 1 | -15/+29 |
| | |||||
* | rebase: block rebase_commit with unstaged changes | Edward Thomson | 2015-04-20 | 1 | -20/+30 |
| | |||||
* | rebase: identify a rebase that has not started | Edward Thomson | 2015-04-20 | 1 | -1/+1 |
| | | | | | | In `git_rebase_operation_current()`, indicate when a rebase has not started (with `GIT_REBASE_NO_OPERATION`) rather than conflating that with the first operation being in-progress. | ||||
* | Plug a few leaks | Carlos Martín Nieto | 2015-03-04 | 1 | -2/+2 |
| | |||||
* | reset: remove reflog message override | Carlos Martín Nieto | 2015-03-03 | 1 | -1/+1 |
| | | | | | This function is meant to simulate what git does in the reset command, so we should include the reflog message in that. | ||||
* | Remove the signature from ref-modifying functions | Carlos Martín Nieto | 2015-03-03 | 1 | -11/+12 |
| | | | | | | | | | | The signature for the reflog is not something which changes dynamically. Almost all uses will be NULL, since we want for the repository's default identity to be used, making it noise. In order to allow for changing the identity, we instead provide git_repository_set_ident() and git_repository_ident() which allow a user to override the choice of signature. | ||||
* | rebase: check alloc result | Edward Thomson | 2015-02-27 | 1 | -0/+1 |
| | |||||
* | Merge pull request #2831 from ethomson/merge_lock | Carlos Martín Nieto | 2015-02-15 | 1 | -6/+9 |
|\ | | | | | merge: lock index during the merge (not just checkout) | ||||
| * | indexwriter: an indexwriter for repo operations | Edward Thomson | 2015-02-14 | 1 | -22/+8 |
| | | | | | | | | | | Provide git_indexwriter_init_for_operation for the common locking pattern in merge, rebase, revert and cherry-pick. | ||||
| * | merge-like operations: lock index while working | Edward Thomson | 2015-02-14 | 1 | -3/+20 |
| | | |||||
* | | rebase: `CHECKOUT_SAFE` instead of `FORCE` | Edward Thomson | 2015-02-13 | 1 | -8/+12 |
| | | | | | | | | | | Switch to a standard branch-switching pattern of a `SAFE` checkout, then updating `HEAD`. | ||||
* | | rebase: allow `NULL` branch to indicate `HEAD` | Edward Thomson | 2015-02-13 | 1 | -2/+16 |
| | | | | | | | | | | Don't require the branch to rebase, if given `NULL`, simply look up `HEAD`. | ||||
* | | rebase: provide NULL `exec` on non-EXEC operations | Edward Thomson | 2015-02-13 | 1 | -9/+28 |
|/ | | | | | Users may want to try to pay attention to the `exec` field on all rebase operations. | ||||
* | 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. |