Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
G
git2
Overview
Overview
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
lvzhengyang
git2
Commits
958950b6
Commit
958950b6
authored
May 01, 2015
by
Edward Thomson
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
stash: document merge conflicts
parent
f0957589
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
11 additions
and
13 deletions
+11
-13
include/git2/stash.h
+11
-13
No files found.
include/git2/stash.h
View file @
958950b6
...
@@ -82,19 +82,16 @@ typedef enum {
...
@@ -82,19 +82,16 @@ typedef enum {
/**
/**
* Apply a single stashed state from the stash list.
* Apply a single stashed state from the stash list.
*
*
* If any untracked or ignored file saved in the stash already exist in the
* If local changes in the working directory conflict with changes in the
* workdir, the function will return GIT_EEXISTS and both the workdir and index
* stash then GIT_EMERGECONFLICT will be returned. In this case, the index
* will be left untouched.
* will always remain unmodified and all files in the working directory will
*
* remain unmodified. However, if you are restoring untracked files or
* If local changes in the workdir would be overwritten when applying
* ignored files and there is a conflict when applying the modified files,
* modifications saved in the stash, the function will return GIT_EMERGECONFLICT
* then those files will remain in the working directory.
* and the index will be left untouched. The workdir files will be left
* unmodified as well but restored untracked or ignored files that were saved
* in the stash will be left around in the workdir.
*
*
* If passing the GIT_APPLY_REINSTATE_INDEX flag and there would be conflicts
* If passing the GIT_APPLY_REINSTATE_INDEX flag and there would be conflicts
* when reinstating the index, the function will return GIT_E
UNMERGED and both
* when reinstating the index, the function will return GIT_E
MERGECONFLICT
*
the workdir and index will be left untouch
ed.
*
and both the working directory and index will be left unmodifi
ed.
*
*
* @param repo The owning repository.
* @param repo The owning repository.
* @param index The position within the stash list. 0 points to the
* @param index The position within the stash list. 0 points to the
...
@@ -102,8 +99,9 @@ typedef enum {
...
@@ -102,8 +99,9 @@ typedef enum {
* @param checkout_options Options to control how files are checked out
* @param checkout_options Options to control how files are checked out
* @param flags Flags to control the applying process. (see GIT_APPLY_* above)
* @param flags Flags to control the applying process. (see GIT_APPLY_* above)
*
*
* @return 0 on success, GIT_ENOTFOUND if there's no stashed state for the given
* @return 0 on success, GIT_ENOTFOUND if there's no stashed state for the
* index, or error code. (see details above)
* given index, GIT_EMERGECONFLICT if changes exist in the working
* directory, or an error code
*/
*/
GIT_EXTERN
(
int
)
git_stash_apply
(
GIT_EXTERN
(
int
)
git_stash_apply
(
git_repository
*
repo
,
git_repository
*
repo
,
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment