| 12:44:18 | | irisfreckles13 joins |
| 16:18:29 | | DogsRNice joins |
| 16:32:42 | | Webuser489423 joins |
| 16:34:02 | <Webuser489423> | Quick question about wikiteam3: Is it possible to update an already-completed dump incrementally? (meaning you get only the history/images that haven't been saved already) |
| 16:34:42 | <justauser> | You are not the first person to ask for this feature, but I don't know of a way. |
| 16:34:54 | <justauser> | And it would be potentially inconsistent. |
| 16:36:02 | <Webuser489423> | Are you referring to the chance of an admin "burning" pages and creating a new page with a completely different history? |
| 16:38:36 | <Webuser489423> | In that case could I at least reuse the already saved images to avoid having to grab 50+GB of redundant image data? |
| 16:39:10 | <justauser> | This would be reasonably doable to do by hand. |
| 16:40:05 | <justauser> | Interrupt the WT3 when it gets image list but before it DL's much, diff new list against the old one, only keep changed lines. |
| 16:40:23 | <justauser> | Untested, but shouldn't wreak much havoc. |
| 16:41:24 | <justauser> | For some extra effect, only look at SHAs when diffing - this would avoid fetching a file that was merely renamed. |
| 16:41:46 | <justauser> | s/changed/changed or new/ |
| 17:16:17 | | ThreeHM quits [Ping timeout: 272 seconds] |
| 17:18:05 | | ThreeHM (ThreeHeadedMonkey) joins |
| 17:36:33 | | Webuser489423 quits [Client Quit] |
| 18:11:55 | | irisfreckles13 quits [Read error: Connection reset by peer] |
| 22:08:30 | | Sluggs (Sluggs) joins |
| 23:16:35 | | atphoenix_ (atphoenix) joins |
| 23:19:49 | | atphoenix__ quits [Ping timeout: 272 seconds] |