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

close

Browse source
This commit is contained in:
Joey Hess 2023-01-16 13:57:54 -04:00
parent 817b06b439
commit 4229e6761e
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 18 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
doc/todo/Wishlist__58___sanitychecker_fix_wrong_UUID__47__duplicate_remote.mdwn
View file

@ -5,3 +5,5 @@ Once the two clients sync they will both have two remotes with the same name. Bu
It would be nice to have some (automatic?) way to resolve this conflict. It would be nice to have some (automatic?) way to resolve this conflict.
Not sure if anything sane can be done if both clients have pushed? Not sure if anything sane can be done if both clients have pushed?
> [[done]] see comment --[[Joey]]

16
doc/todo/Wishlist__58___sanitychecker_fix_wrong_UUID__47__duplicate_remote/comment_1_a9e54e4bc540cbab7cdbbfdeaa973f4a._comment Normal file
View file

@ -0,0 +1,16 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2023-01-16T17:54:51Z"
content="""
This does not make sense to me. If the remote is a git repo,
it will be initialized by git-annex only once, so there will only be one
UUID. The second "client" that uses that remote will see the earlier UUID.
Unless there were some kind of a race in initializing the same repo
concurrently, but that seems unlikely and if so this is lacking in any
details about it.
I'm going to close this since it does not make sense, but do followup if
you remember what this was supposed to be about.
"""]]