From 20b0e563ce147937449efef13845d682d7ee40b1 Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Wed, 26 Mar 2003 11:44:04 +0000 Subject: mention the URL to the mailing lists --- docs/BUGS | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) (limited to 'docs/BUGS') diff --git a/docs/BUGS b/docs/BUGS index d84f60b60..d9bff3679 100644 --- a/docs/BUGS +++ b/docs/BUGS @@ -8,7 +8,7 @@ $Id$ BUGS Curl and libcurl have grown substantially since the beginning. At the time - of writing (end of April 2002), there are 32000 lines of source code, and by + of writing (end of March 2003), there are 35000 lines of source code, and by the time you read this it has probably grown even more. Of course there are lots of bugs left. And lots of misfeatures. @@ -19,18 +19,21 @@ BUGS WHERE TO REPORT If you can't fix a bug yourself and submit a fix for it, try to report an as - detailed report as possible to the curl mailing list to allow one of us to + detailed report as possible to a curl mailing list to allow one of us to have a go at a solution. You should also post your bug/problem at curl's bug tracking system over at http://sourceforge.net/bugs/?group_id=976 - (but please read the section below first before doing that) + (but please read the sections below first before doing that) + + If you feel you need to ask around first, find a suitable mailing list and + post there. The lists are available on http://curl.haxx.se/mail/ WHAT TO REPORT When reporting a bug, you should include information that will help us - understand what's wrong what you expected to happen and how to repeat the + understand what's wrong, what you expected to happen and how to repeat the bad behavior. You therefore need to tell us: - your operating system's name and version number (uname -a under a unix -- cgit v1.2.3