Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 2392  |
|  August Abolins to Martin Foster  |
|  oxp: Nodelist problem  |
|  11 Mar 21 07:10:00  |
 MSGID: 2:221/1.58@fidonet ee57de4e REPLY: 2:310/31.3@fidonet ee521b3d PID: OpenXP/5.0.49 (Win32) CHRS: ASCII 1 TZUTC: -0500 Hello Martin! ** On Thursday 11.03.21 - 11:10, you wrote to me: AA>> Huh? Isn't the "true purpose" to tell OXP that it is OK AA>> to kickstart the nodelist updates when a new DIFF arrives? MF> Ahbut that's only half the story, it says nothing about the MF> hitherto unknown fact that a nodelist can be MF> updated(overwritten) with a new full nodelist. The way I MF> see it is that the true purpose is that a nodelist can be MF> updated either by using a diff or by using a full nodelist, MF> depending on whether the switch is on or off. AH! I like *that* explanation. Put *that* in the Helps. ;) I had no idea that oxp could utilize incoming "full" nodelists and update the config that way. I thought the updates only pertained to diffs if/when they arrived. And otherwise if the diff setting was disabled, I thought that NOTHING would happen with the incoming files - and require manual processing. -- ../|ug --- OpenXP 5.0.49 * Origin: The ONLY point that matters! --> . <-- (2:221/1.58) SEEN-BY: 1/123 90/1 105/81 120/340 123/131 124/5016 129/305 154/10 SEEN-BY: 203/0 221/1 6 360 226/30 227/114 702 229/101 424 426 664 SEEN-BY: 229/1016 1017 240/2100 5138 5411 5824 5832 5853 249/206 317 SEEN-BY: 249/400 280/464 5003 282/1038 288/100 292/854 8125 310/31 SEEN-BY: 317/3 320/219 322/757 342/200 396/45 423/81 120 712/848 770/1 SEEN-BY: 2432/390 2452/250 2454/119 PATH: 221/1 280/464 240/5832 229/426 |
[ << oldest | < older | list | newer > | newest >> ]