When I reported this problem with Bash last year, I looked at the Gnu website for information on how to contribute and report bugs. And although the man page is exactly what you show, the website still direct it diferently - and maybe it is nearly the same I saw last year: "For development sources, bug and patch trackers, and other information, please see the Bash project page at savannah.gnu.org."
http://www.gnu.org/software/bash/#contribute I'll also point this in their mailing list. Thank you both for these comments, Paul and Assaf. Regards, Balaco On Tue, Jun 2, 2015, at 10:42, Paul Smith wrote: > On Tue, 2015-06-02 at 07:26 -0400, Julian Marchant wrote: > > I think you may be projecting an impression you have on a few Savannah > > projects onto the entire Savannah site. I'm sure there are some > > projects on Savannah which are inactive. > > I think the more accurate statement is that there are a few projects > which are inactive _on Savannah_. > > Savannah hasn't been around all that long in the history of the FSF / > GNU project, and many projects predate it. Although most of those > projects may have a presence on Savannah now, often they still use > traditional methods of managing the project (mostly mailing lists) > rather than the Savannah facilities. There's no mandate that a GNU > project MUST use Savannah for project management. > > For bash, in particular, the bash(1) man page has an extensive section > on how to report bugs and nowhere does it mention Savannah. > > From bash(1) BUG REPORTS: > > > Once you have determined that a bug actually exists, use the bashbug > > command to submit a bug report. If you have a fix, you are encouraged > > to mail that as well! Suggestions and `philosophical' bug reports may > > be mailed to [email protected] or posted to the Usenet newsgroup > > gnu.bash.bug. > > > -- http://www.fastmail.com - mmm... Fastmail...
