Hi,
I noticed, that
git annex copy --to REMOTE FILES
and
git annex copy --to REMOTE --not --in REMOTE FILES
behave differently. The first does not check, whether file contents are already in the remote the latter does that. I realize that this mimics "normal" (UNIX) copy behaviour but I was not entirely certain this was desired. Depending on the type of the remote and its configuration (encryption) the latter is considerably faster.
Just my two cents.
git annex copy --fasthas the same behavior as--not --in REMOTEThe reason this is not the default behavior is that git-annex's location tracking information can sometimes be out of date, and then those two will not copy some files despite their content not being any longer in the remote. This won't lead to data loss, but could result in unexpected behavior, and so the slower, more understandable behavior is used by default. (Although I sometimes go back and forth on switching it.)