From e78050c808aac5392ac0a963bdd090ecebc2175b Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 6 Sep 2019 12:31:01 -0400 Subject: [PATCH] followup --- ..._44c082a9321806ca2a60debf829f9c39._comment | 22 +++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 doc/bugs/git-annex-sync_not_quite_idempotent__63__/comment_4_44c082a9321806ca2a60debf829f9c39._comment diff --git a/doc/bugs/git-annex-sync_not_quite_idempotent__63__/comment_4_44c082a9321806ca2a60debf829f9c39._comment b/doc/bugs/git-annex-sync_not_quite_idempotent__63__/comment_4_44c082a9321806ca2a60debf829f9c39._comment new file mode 100644 index 0000000000..5c7a6e3233 --- /dev/null +++ b/doc/bugs/git-annex-sync_not_quite_idempotent__63__/comment_4_44c082a9321806ca2a60debf829f9c39._comment @@ -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. +"""]]