Enrico Zini wrote: > first of all, thank you for git-annex. > > I have three repositories: > > laptop (my laptop) > archive (the big 2T archive USB disk) > desktop (my old desktop, which I'm using mostly as a backup) > > And a file I care about: > > laptop:/store$ git annex whereis file.ext > whereis file.ext (1 copy) > xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx -- archive (Archivio 2T usb drive) > ok > > I'm on my laptop and I'd like a copy of file.ext to be backed up to my old > desktop: > > laptop:/store$ git annex copy file.ext --to=desktop > laptop:/store$ echo $? > 0 > > This said nothing and did nothing, successfully :(
Yes, all git-annex commands silenty skip files they can't or don't need to act on. This is done because it's not uncommon to have a lot of files in a tree, many of which are really present, and many not; it's then nice to be able to copy/drop all the ones that are present, or get all the ones that are not without manually specifying, and without drowning in warning messages. I think that this becomes clear once you get used to it and see that it always says what it's doing, so a silent output like this was a no-op. I can see how it can be initially confusing though. Perhaps you can suggest some documentation improvements in this area? -- see shy jo
signature.asc
Description: Digital signature
