diff options
author | 2014-07-11 16:45:18 -0400 | |
---|---|---|
committer | 2014-07-11 16:45:18 -0400 | |
commit | 2a727e8c5f8d003af7102ea7de22e45a5faec421 (patch) | |
tree | 661d008aeb7f13c873c9afb7dcfa360aed60a528 /doc/git-annex.mdwn | |
parent | 64b74f4c616bd1aa42e7833b449586b64dac1ba5 (diff) |
resolvemerge: New plumbing command that runs the automatic merge conflict resolver.
Diffstat (limited to 'doc/git-annex.mdwn')
-rw-r--r-- | doc/git-annex.mdwn | 14 |
1 files changed, 12 insertions, 2 deletions
diff --git a/doc/git-annex.mdwn b/doc/git-annex.mdwn index dc3249456..6dde7c516 100644 --- a/doc/git-annex.mdwn +++ b/doc/git-annex.mdwn @@ -170,8 +170,8 @@ subdirectories). * `merge` - This performs the same merging that is done by the sync command, but - without pushing or pulling any data. + This performs the same merging (and merge conflict resolution) + that is done by the sync command, but without pushing or pulling any data. One way to use this is to put `git annex merge` into a repository's post-receive hook. Then any syncs to the repository will update its working @@ -939,6 +939,16 @@ subdirectories). Most MATCHING OPTIONS can be used with findref, to limit the files it finds. However, the --include and --exclude options will not work. +* `resolvemerge` + + Resolves a conflicted merge, by adding both conflicting versions of the + file to the tree, using variants of their filename. This is done + automatically when using `git annex sync` or `git annex merge`. + + Note that only merge conflicts that involve an annexed file are resolved. + Merge conflicts between two files that are not annexed will not be + automatically resolved. + * `test` This runs git-annex's built-in test suite. |