As a end user, it gives the impression that the system is shaky. Now, this is written out of frustration: I spent while documenting a set of classes only to get the thing to a VM crash when posting to monticello and followed by the inability to get the work back without copy/pasting stuff all over again since the changes files wouldn't work (and is full of <historical> entries).
Well, that's what it has to do with each other: the workflow is broken and it demotivated me from documenting classes again. Preventing contribution is not good. Especially given the boatload of undocumented items. Phil On Sun, Jun 9, 2013 at 6:35 PM, Marcus Denker <[email protected]>wrote: > > On Jun 9, 2013, at 5:55 PM, [email protected] wrote: > > well, if basic comments have issues (first with historical then with > change files) I don't give a damn about links. That's what. > > > But all these things have *nothing* to do with each other! > > It really does not help to mix up issues… > > Marcus > >
