diff options
author | Joey Hess <joeyh@joeyh.name> | 2017-04-07 12:47:42 -0400 |
---|---|---|
committer | Joey Hess <joeyh@joeyh.name> | 2017-04-07 12:47:42 -0400 |
commit | 7f6836b2e423dab040e00425fedaada2b44c7596 (patch) | |
tree | 6d421364d00e60268d0c0d905fa610a15f42d66c | |
parent | 933b09f3f90ffe39e1700cd1be685d30bc3835ab (diff) |
confused user, not a bug
2 files changed, 27 insertions, 0 deletions
diff --git a/doc/bugs/cause__58___fake_annex_repo___124___result__58___inflated_numcopies___124___workaround__58___initialize_properly.mdwn b/doc/bugs/cause__58___fake_annex_repo___124___result__58___inflated_numcopies___124___workaround__58___initialize_properly.mdwn index 7e4d81d03..fc098bb84 100644 --- a/doc/bugs/cause__58___fake_annex_repo___124___result__58___inflated_numcopies___124___workaround__58___initialize_properly.mdwn +++ b/doc/bugs/cause__58___fake_annex_repo___124___result__58___inflated_numcopies___124___workaround__58___initialize_properly.mdwn @@ -80,3 +80,5 @@ upgrade supported from repository versions: 0 1 2 3 4 5 operating system: linux x86_64 </pre> + +> [[done]] appears to be a confused user, not a bug. --[[Joey]] diff --git a/doc/bugs/cause__58___fake_annex_repo___124___result__58___inflated_numcopies___124___workaround__58___initialize_properly/comment_2_13989894486a9ff9f243c6b2071d788f._comment b/doc/bugs/cause__58___fake_annex_repo___124___result__58___inflated_numcopies___124___workaround__58___initialize_properly/comment_2_13989894486a9ff9f243c6b2071d788f._comment new file mode 100644 index 000000000..5ffd00d71 --- /dev/null +++ b/doc/bugs/cause__58___fake_annex_repo___124___result__58___inflated_numcopies___124___workaround__58___initialize_properly/comment_2_13989894486a9ff9f243c6b2071d788f._comment @@ -0,0 +1,25 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 2""" + date="2017-04-07T16:42:11Z" + content=""" +This bug report is, to the best of my knowledge, totally wrong. + +Yes, git-annex sync pushes the git-annex branch to all git remotes. +This is intentional, and not a problem. That is just a git branch. +It's helpful to push it to eg, github, if you want to be able to pull it +from there into another clone. Pushing the git-annex branch to github does +*not* make git-annex think that github is holding the contents of annexed +files. + +In your "reproduction" section, I think you forgot to run `git annex sync` +in Zeta, so its working tree had not been updated with the files synced to +it from Alpha, which is why `git annex list` didn't show anything. Or +somethig like that. You did not provide quite enough information to guess +what you were doing. + +I'm going to close this. If you think it is still a problem, please provide +either a detailed transcript demontrating the problem or enough information +to reporoduce the problem, starting with an empty directory and +constructing the necessary git repositories to demonstrate the problem. +"""]] |