mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions 1

removed

Browse source
This commit is contained in:
https://www.google.com/accounts/o8/id?id=AItOawn3p4i4lk_zMilvjnJ9sS6g2nerpgz0Fjc 2014-03-23 23:00:44 +00:00 • committed by admin
parent 82c3603704
commit 1124a7d8bd
1 changed files with 0 additions and 16 deletions
Download patch file Download diff file Expand all files Collapse all files

16
doc/automatic_conflict_resolution/comment_4_5a208ecefd02916cc86e40272923ca3e._comment
View file

@ -1,16 +0,0 @@
[[!comment format=mdwn
username="https://www.google.com/accounts/o8/id?id=AItOawn3p4i4lk_zMilvjnJ9sS6g2nerpgz0Fjc"
nickname="Matthias"
subject="merge only for metadata branch?"
date="2014-03-23T22:59:52Z"
content="""
As far as I observed, \"git annex merge\" only merges the \"git-annex\" branch. My wish is to have the conflict resolution from \"git annex sync\" in the \"master\" branch, but no automatic commit, such that the user can verify and possibly correct the merge. The proposed merge could go to the index. Consider the following scenario:
1. We have repo A, B, and CENTRAL
2. All three start with a root commit in \"master\" branch
3. Then A commits a file \"test.txt\" with content \"a\" and syncs with SERVER
4. Meanwhile, B commits \"test.txt\" with content \"b\"
5. When B tries to sync with SERVER, the proposed conflict resolution having two files \"test.txt-variantXXXX\" and \"test.txt-variantYYYY\" should be staged in the index, but not committed yet.
6. B can now commit a custom merge, e.g. with file content \"ab\".
The point is that I really like the conflict resolution, but still want to force the user to check the result.
"""]]