continue importing even if some directories can't be read
Submitted by Adam Dingle
Link to original bug (#717360)
Description
---- Reported by adam@yorba.org 2011-03-14 08:30:00 -0700 ----
Original Redmine bug id: 3341
Original URL: http://redmine.yorba.org/issues/3341
Searchable id: yorba-bug-3341
Original author: Adam Dingle
Original description:
A user on the mailing list has suggested that Shotwell should continue an import operation even if some directories can't be read:
http://lists.yorba.org/pipermail/shotwell/2011-March/001872.html
---- Additional Comments From shotwell-maint@gnome.bugs 2013-05-16 14:32:00 -0700 ----
History
Comment 1
Updated by Adam Dingle over 2 years ago
(Autoimporting does already continue in this situation, it seems.)
Comment 2
Updated by Jim Nelson 11 months ago
- Target version set to 0.14.0
Comment 3
Updated by Jim Nelson 11 months ago
- Category set to ux
Comment 4
Updated by Jim Nelson 10 months ago
- Target version changed from 0.14.0 to 0.15.0
Comment 5
Updated by Jim Nelson 8 months ago
- Description updated (diff)
- Category changed from ux to import
- Priority changed from Low to Normal
Comment 6
Updated by Jim Nelson 6 months ago
-
Target version deleted (
<strike>
_0.15.0_</strike>
)
--- Bug imported by chaz@yorba.org 2013-11-25 21:51 UTC ---
This bug was previously known as bug 3341 at http://redmine.yorba.org/show_bug.cgi?id=3341
Unknown version " in product shotwell. Setting version to "!unspecified". Unknown milestone "unknown in product shotwell. Setting to default milestone for this product, "---". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one. Resolution set on an open status. Dropping resolution