diff options
author | Joey Hess <joeyh@joeyh.name> | 2015-10-06 17:29:44 -0400 |
---|---|---|
committer | Joey Hess <joeyh@joeyh.name> | 2015-10-06 17:29:44 -0400 |
commit | 4233e81ef174d7891a8134656a67a6d40ea09ef9 (patch) | |
tree | d03021cbc2109db805de60220dfff7272719122a /doc | |
parent | 9e2cea9f7a3fdea641371cd59f313a4cc6dc1630 (diff) |
copy --auto was checking the wrong repo's preferred content. (--from was checking what --to should, and vice-versa.) Fixed this bug, which was introduced in version 5.20150727.
Diffstat (limited to 'doc')
-rw-r--r-- | doc/bugs/git_annex_preferred_content_strange_behavior.mdwn | 2 | ||||
-rw-r--r-- | doc/bugs/git_annex_preferred_content_strange_behavior/comment_4_6e0f6ec54098f6e8fde80f733dd9c124._comment | 8 |
2 files changed, 10 insertions, 0 deletions
diff --git a/doc/bugs/git_annex_preferred_content_strange_behavior.mdwn b/doc/bugs/git_annex_preferred_content_strange_behavior.mdwn index 89d6cac90..4ee0d5194 100644 --- a/doc/bugs/git_annex_preferred_content_strange_behavior.mdwn +++ b/doc/bugs/git_annex_preferred_content_strange_behavior.mdwn @@ -49,3 +49,5 @@ git annex copy --to b --auto # now, it copies the file to b. Why ?? ### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders) Definitely! git-annex is a wonderful tool that I have been using every day to manage all my files for 2 years now. Thank you for this excellent software. + +> [[fixed|done]] --[[Joey]] diff --git a/doc/bugs/git_annex_preferred_content_strange_behavior/comment_4_6e0f6ec54098f6e8fde80f733dd9c124._comment b/doc/bugs/git_annex_preferred_content_strange_behavior/comment_4_6e0f6ec54098f6e8fde80f733dd9c124._comment new file mode 100644 index 000000000..78cde3616 --- /dev/null +++ b/doc/bugs/git_annex_preferred_content_strange_behavior/comment_4_6e0f6ec54098f6e8fde80f733dd9c124._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 4""" + date="2015-10-06T21:28:43Z" + content=""" +Indeed, the logic got switched to opposite it should during the +optparse-applicative transition. +"""]] |