comparison doc/interpreter/contrib.txi @ 17680:4264c78951ec

doc: refer to patch tracker instead of mailing list for bugs. * doc/interpreter/contrib.txi (How to Contribute): Mention patch tracker.
author Rüdiger Sonderfeld <ruediger@c-plusplus.de>
date Tue, 08 Oct 2013 13:38:37 +0200
parents cdeadf62663f
children d63878346099
comparison
equal deleted inserted replaced
17679:c81debf315e0 17680:4264c78951ec
34 * Other Sources:: 34 * Other Sources::
35 @end menu 35 @end menu
36 36
37 @node How to Contribute 37 @node How to Contribute
38 @section How to Contribute 38 @section How to Contribute
39 The mailing list for Octave development discussion and sending 39 The mailing list for Octave development discussion is
40 contributions is @email{maintainers@@octave.org}. This concerns the 40 @email{maintainers@@octave.org}. Patches should be submitted to
41 development of Octave core, i.e., code that goes to Octave directly. 41 @url{https://savannah.gnu.org/patch/?func=additem&group=octave, Octave's patch tracker}.
42 You may consider developing and publishing a package instead; a great 42 This concerns the development of Octave core, i.e., code that goes to Octave
43 place for this is the allied Octave-Forge project 43 directly. You may consider developing and publishing a package instead;
44 (@url{http://octave.sourceforge.net}). Note that the Octave core project is 44 a great place for this is the allied Octave-Forge project
45 inherently more conservative and follows narrower rules. 45 (@url{http://octave.sourceforge.net}). Note that the Octave core
46 project is inherently more conservative and follows narrower rules.
46 47
47 @node Building the Development Sources 48 @node Building the Development Sources
48 @section Building the Development Sources 49 @section Building the Development Sources
49 50
50 The directions for building from the Development sources change from 51 The directions for building from the Development sources change from