Activity log for bug #62291
| Date | Who | What changed | Old value | New value | Message |
|---|---|---|---|---|---|
| 2006-09-25 12:11:48 | Hervé Fache | bug | added bug | ||
| 2006-09-25 13:30:48 | Simon Law | bug | assigned to kdebase (upstream) | ||
| 2006-09-25 14:24:28 | Rocco Stanzione | kdebase: importance | Untriaged | Wishlist | |
| 2006-09-25 14:24:28 | Rocco Stanzione | kdebase: statusexplanation | I've never expected this behavior (successfully using an image that's been removed) but it would be a very nice feature. I wouldn't feel so nervous about moving my image directories around. | ||
| 2006-09-27 07:40:27 | Bug Watch Updater | kdebase: status | Unknown | Confirmed | |
| 2006-09-27 14:33:00 | Anthony Mercatante | kdebase: status | Unconfirmed | Rejected | |
| 2006-09-27 14:33:00 | Anthony Mercatante | kdebase: statusexplanation | I've never expected this behavior (successfully using an image that's been removed) but it would be a very nice feature. I wouldn't feel so nervous about moving my image directories around. | I'm rejecting this for 3 reasons : - caches are *evil* and are to be avoided as much as possible, since it is a pain for the user to figure out what happens when it gets corrupted (look at the DNS cache on Windows XP for a good example). - that normal behavior, and implementing this would mean lots of work or a very, very low usage. - why not the same over smb shares, ftp, nfs or any remove location accessible via vfs or ioslmave ? If we start even thinking of implement this, we would never see the end... | |
| 2011-02-27 22:43:57 | Bug Watch Updater | kdebase: importance | Unknown | Wishlist | |
| 2013-05-09 00:31:37 | Bug Watch Updater | kde-baseapps: status | Confirmed | Unknown |
