Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 2390  |
|  Martin Foster to August Abolins  |
|  oxp: Nodelist problem  |
|  11 Mar 21 11:10:00  |
 MSGID: 2:310/31.3@fidonet ee521b3d REPLY: 2:221/1.58@fidonet ee47c355 PID: OpenXP/5.0.49 (Win32) CHRS: ASCII 1 TZUTC: 0000 Hello August! *** Tuesday 09.03.21 at 08:01, August Abolins wrote to Martin Foster: [snip] AA>>> The English help is a bit closer because it says "...to AA>>> process the diff update". MF>> Yes but it says "OpenXP will call its own nodelist MF>> processor to process the diff update". Well yes, it will, MF>> but that doesn't describe the true purpose of this MF>> particular option. AA> Huh? Isn't the "true purpose" to tell OXP that it is OK to AA> kickstart the nodelist updates when a new DIFF arrives? Ahbut that's only half the story, it says nothing about the hitherto unknown fact that a nodelist can be updated(overwritten) with a new full nodelist. The way I see it is that the true purpose is that a nodelist can be updated either by using a diff or by using a full nodelist, depending on whether the switch is on or off. Regards, Martin --- OpenXP 5.0.49 * Origin: Bitz-Box - Bradford - UK (2:310/31.3) SEEN-BY: 1/123 90/1 105/81 120/340 123/131 124/5016 129/305 154/10 SEEN-BY: 203/0 221/0 226/30 227/114 702 229/101 424 426 664 1016 1017 SEEN-BY: 240/2100 5138 5411 5824 5832 5853 249/206 317 400 280/464 SEEN-BY: 280/5003 282/1038 288/100 292/854 8125 310/31 317/3 320/219 SEEN-BY: 322/757 342/200 396/45 423/120 712/848 770/1 2432/390 2452/250 SEEN-BY: 2454/119 PATH: 310/31 280/464 240/5832 229/426 |
[ << oldest | < older | list | newer > | newest >> ]