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

followup

Browse source
This commit is contained in:
Joey Hess 2019-09-06 12:31:01 -04:00
parent 218afb9c0f
commit e78050c808
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 22 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

22
doc/bugs/git-annex-sync_not_quite_idempotent__63__/comment_4_44c082a9321806ca2a60debf829f9c39._comment Normal file
View file

@ -0,0 +1,22 @@
[[!comment format=mdwn
username="joey"
subject="""comment 4"""
date="2019-09-06T16:08:19Z"
content="""
The second transcript seems to show that the first sync never
tries to push to origin. Then the second sync does push to origin. Then the
third sync doesn't push to origin. Since sync always pushes to origin
unless remote.name.annex-push or remote.name.annex-readonly are set,
I remain confused why successive runs would sometimes push and other times
not push.
(It also appears as if stderr output is sometimes appearing before
stdout output that actually comes first. Which makes me not trust this
transcript's paste accuracy either, or maybe something to do with the
terminal is resulting in this unusual output ordering.)
Also, the second sync found one modified file to commit, so something must
have modified that file in between the two sync runs. If a file gets
modified in between two sync runs, they will of course not do the same
thing.
"""]]