when workTreeItems finds a problem with a parameter, don't go on to process it
authorJoey Hess <joeyh@joeyh.name>
Thu, 6 Aug 2020 17:47:45 +0000 (13:47 -0400)
committerJoey Hess <joeyh@joeyh.name>
Thu, 6 Aug 2020 17:47:45 +0000 (13:47 -0400)
commit5d380c6c5cbca4637840236d382ad69ce1d84805
tree18e38d4948c7a1cc890b534e097410d81d863ffe
parent8312cac018f198dc27037127afd42fe219b0340d
when workTreeItems finds a problem with a parameter, don't go on to process it

Part of workTreeItems is trying detect a case
where git porcelain refuses to process a file, and where
git ls-files silently outputs nothing. But, it's hard to perfectly
replicate git's behavior, and besides, git's behavior could change.
So it could be that we warn, but then git ls-files does not skip over
it, and so git-annex also processes it after warning about it.

So, if we think we have a problem with a parameter, display the warning,
and skip processing it at all.

Implementing this was complicated by needing to handle the case where
all command-line parameters get filtered out this way. Which is
different than the case where there are none, because we don't want to
operate on all files in this new case..
CmdLine/Seek.hs
Command/Sync.hs
doc/bugs/__39__Beyond_symbolic__39___link_error_when_link_is_upstream_of_repo/comment_1_a2d1112b0a9338b7c093546a985a5f90._comment [new file with mode: 0644]
doc/bugs/__39__Beyond_symbolic__39___link_error_when_link_is_upstream_of_repo/comment_2_c6e30af134a73bc8b3faee83c7c3b378._comment [new file with mode: 0644]