bug fix submissions

[pdelong]

I made a handful of corrections to the manual (mostly cosmetic), and wanted to submit it back to the codebase.

In general, if I were to find a bug and fix it, how would I go about submitting it for review by the maintainers? Should I post it here or email it to someone? Would you prefer the whole changed file, or a patch/diff of the file?

[raX]

It really depends on how much you've fixed. If you have a few fixes here and there, go ahead and send me a patch. If the patch is too big and covers many files, it may take me quite a while to merge it into cacti's code.

The other option is to do it yourself. I do not currently have the 0.6.x branch available via CVS, but if you're brave enough I could give you access to 0.8 and you could make your changes there.

Tell me what you think.

-Ian

[pdelong]

I knew there was a "raxnet" project up at SourceForge, but until now I didn't realize that the "cacti" project was up there too.

So I went to look at the codebase, and a quick diff seems to show that the manual has changed significantly between 0.6.8 and 0.8. My changes are based on 0.6.8, so I'd have to do it again for 0.8. Plus, I don't know if I want to take-on the accoutability of having CVS access yet. I'm not yet comfortable enough with PHP to go mucking-about with the code (though it looks a lot like Perl).

I think for now I'll just email you a drop-in replacement for the 0.6.8 manual. I mostly just changed a line here and there. Just do a diff to see what I did.