summaryrefslogtreecommitdiff
path: root/tests/stash/apply.c
Commit message (Collapse)AuthorAgeFilesLines
* stash: const up conflict paramsEdward Thomson2015-06-291-1/+1
|
* stash: test we apply using reflog-like indicesEdward Thomson2015-06-261-0/+34
|
* stash: stage new files when unstashing themEdward Thomson2015-06-251-2/+50
| | | | | Files that were new (staged additions) in the stash tree should be staged when unstashing, even when not applying the index.
* stash: don't allow apply with staged changesEdward Thomson2015-06-251-1/+18
|
* stash apply: add a newly staged file to testsEdward Thomson2015-06-251-8/+19
|
* Fixed index being double-freed in stash testsPierre-Olivier Latour2015-06-201-2/+0
|
* Fixed build warnings on Xcode 6.1Pierre-Olivier Latour2015-06-021-1/+7
|
* Rename GIT_EMERGECONFLICT to GIT_ECONFLICTEdward Thomson2015-05-291-5/+5
| | | | | | | | | | We do not error on "merge conflicts"; on the contrary, merge conflicts are a normal part of merging. We only error on "checkout conflicts", where a change exists in the index or the working directory that would otherwise be overwritten by performing the checkout. This *may* happen during merge (after the production of the new index that we're going to checkout) but it could happen during any checkout.
* Fix a few leaksCarlos Martín Nieto2015-05-131-0/+2
| | | | | The interesting one is the notification macro, which was returning directly on a soft-abort instead of going through the cleanup.
* stash_apply: provide progress callbacksEdward Thomson2015-05-111-0/+45
|
* stash_apply: provide its own options structureEdward Thomson2015-05-111-17/+38
|
* stash: test checkout notify callbacksEdward Thomson2015-05-111-0/+52
|
* stash: return GIT_EMERGECONFLICT on merge conflictEdward Thomson2015-05-111-1/+1
|
* stash: refactor to use merge_iteratorsEdward Thomson2015-05-111-12/+12
|
* stash apply: check out a tree, not piecewiseEdward Thomson2015-05-111-2/+2
|
* Added git_stash_apply() and git_stash_pop() APIsPierre-Olivier Latour2015-05-111-0/+215