>> While I'm sure your interest is appreciated by the author, the format you >> have chosen is not appropriate. > > Whereas the documentation itself states as follows. Since you differ, you > might wish to edit that. > > "If you think you have found a bug not described here, please send a report > to fish-us...@lists.sf.net."
This phrase refers directly to a list of known bugs in the software. It does not refer to potential typos in the documentation. Additions to the list of known bugs justifies or even necessitates that the matter is brought to the attention of the subscribers of the mailing list. While important as well, potential typos and capitalisation errors does _not_ warrant that the matter is brought to the attention of the whole mailing list! Would you disagree that the process clone/edit/pull-request procedure I suggested is more appropriate, and far more effective? I hope you take this as constructive input. Becoming familiar with the clone/edit/pull-request workflow would allow you to contribute valuable corrections to open source software in a very effective manner. Something that _would_ be appreciated. Best, Christian ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. This 200-page book is written by three acclaimed leaders in the field. The early access version is available now. Download your free book today! http://p.sf.net/sfu/neotech_d2d_may _______________________________________________ Fish-users mailing list Fish-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fish-users
