Merge branch 'master' of ssh://git-annex.branchable.com
This commit is contained in:
commit
3911b2db13
3 changed files with 32 additions and 0 deletions
|
@ -0,0 +1,12 @@
|
|||
[[!comment format=mdwn
|
||||
username="http://joey.kitenet.net/"
|
||||
nickname="joey"
|
||||
subject="comment 1"
|
||||
date="2012-04-23T14:29:03Z"
|
||||
content="""
|
||||
You handle conflicts in annexed files the same as you would handle them in other binary files checked into git.
|
||||
|
||||
For example, you might choose to `git rm` or `git add` the file to resolve the conflict.
|
||||
|
||||
[[Previous_discussion|forum/A_really_stupid_question]]
|
||||
"""]]
|
|
@ -0,0 +1,10 @@
|
|||
[[!comment format=mdwn
|
||||
username="http://christian.amsuess.com/chrysn"
|
||||
nickname="chrysn"
|
||||
subject="comment 3"
|
||||
date="2012-04-23T14:14:28Z"
|
||||
content="""
|
||||
thanks, that's great. will there be a way to have sharedRepository work for shared remotes (rsync, directory) too, or is that better taken care of by acls?
|
||||
|
||||
@not thought of shared repos: we're having our family photo archive spread over our laptops, and backed up on our home storage server and on an rsync+encryption off-site server, with everyone naturally having their own accounts on all systems -- just if you need a use case.
|
||||
"""]]
|
|
@ -0,0 +1,10 @@
|
|||
[[!comment format=mdwn
|
||||
username="http://joey.kitenet.net/"
|
||||
nickname="joey"
|
||||
subject="comment 4"
|
||||
date="2012-04-23T14:35:39Z"
|
||||
content="""
|
||||
I'm not currently planning to support sharedRepository perms on special remotes. I suppose I could be convinced otherwise, it's perhaps doable for the ones you mention (rsync might be tricky). (bup special remote already supports it of course.)
|
||||
|
||||
thanks for the use case!
|
||||
"""]]
|
Loading…
Reference in a new issue