moparisthebest/curl
1
0
Fork 0
mirror of https://github.com/moparisthebest/curl synced 2024-12-22 08:08:50 -05:00
Code Issues Releases Wiki Activity

mention the URL to the mailing lists

Browse Source
This commit is contained in:
Daniel Stenberg 2003-03-26 11:44:04 +00:00
parent 8b6cf239a3
commit 20b0e563ce
1 changed files with 7 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
docs/BUGS
View File

@ -8,7 +8,7 @@ $Id$
BUGS BUGS
Curl and libcurl have grown substantially since the beginning. At the time 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. the time you read this it has probably grown even more.
Of course there are lots of bugs left. And lots of misfeatures. Of course there are lots of bugs left. And lots of misfeatures.
@ -19,18 +19,21 @@ BUGS
WHERE TO REPORT WHERE TO REPORT
If you can't fix a bug yourself and submit a fix for it, try to report an as 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 have a go at a solution. You should also post your bug/problem at curl's bug
tracking system over at tracking system over at
http://sourceforge.net/bugs/?group_id=976 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 WHAT TO REPORT
When reporting a bug, you should include information that will help us 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: bad behavior. You therefore need to tell us:
- your operating system's name and version number (uname -a under a unix - your operating system's name and version number (uname -a under a unix