bug-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

What do the CVS devs want to see in a bug report? was [Re: init error in


From: Todd Denniston
Subject: What do the CVS devs want to see in a bug report? was [Re: init error in Suse 10.1: cannot get working directory:]
Date: Thu, 26 Jul 2007 13:53:50 -0500
User-agent: Thunderbird 2.0.0.5 (X11/20070716)

Larry Jones wrote, On 07/26/2007 10:48 AM:
Todd Denniston writes:
Would you please:
A) collect appropriate information (processor, 32/64 bit mode, distro & release + update status, version of CVS you compiled).

Also collect the ``configure'' output, please -- for some reason
configure thinks that your native getcwd() is defective (otherwise, it
would have just used it) and we need to know what that is.

-Larry Jones

It's no fun to play games with a poor sport. -- Calvin



Larry,
Could You, Derek and Mark add a section to HACKING or the Appendix H of Cederqvist indicating what you would like to see 90% of the time someone is putting together a bug report?

Attached is my cut a patch to Cederqvist for such a list.

I grant permission to distribute this patch under the terms of the GNU Public License, or what ever permission is appropriate for distribution of the Cederqvist document.

--
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter
--- cvs.texinfo.orig    2006-05-15 19:58:40.000000000 -0500
+++ cvs.texinfo 2007-07-26 13:45:53.000000000 -0500
@@ -14591,7 +14591,8 @@
 came up.
 
 @item
-It is also possible to report bugs to @email{bug-cvs@@nongnu.org}.
+It is also possible to report bugs to @email{bug-cvs@@nongnu.org} 
+or @example @url{http://savannah.nongnu.org/bugs/?group=cvs&address@hidden 
example
 Note that someone may or may not want to do anything
 with your bug report---if you need a solution consider
 one of the options mentioned above.  People probably do
@@ -14614,6 +14615,32 @@
 whatever forum you prefer, but there are not
 necessarily any maintainers reading bug reports sent
 anywhere except @email{bug-cvs@@nongnu.org}.
+
address@hidden
+When reporting problems with @sc{cvs} please include the following information:
address@hidden 
+CVS version [cvs -v or head ccvs/configure.in]
+Did you compile from source or where did you get the binaries?
+What OS distribution and distribution release are you running on?
+The actual error.
+And sometimes, if you built from source, a section of output 
+where 'make check' faults, see @sc{tests}.
address@hidden example
+If your problem includes that the @sc{cvs} is breaking, 
+i.e., the OS is throwing the warning/error instead of @sc{cvs}, 
+please also include:
address@hidden 
+Processor type
+32/64/128 bit mode, if the processor can be ran in two or more modes
+The actual error, cut and paste not summarized.
address@hidden example
+If it seems to you that CVS is being built with a CVS replacement 
+function where you think it should use one provided by the OS, 
+or vis-versa [such as xgetcwd instead of getcwd]. 
+along with the above include:
address@hidden 
+configure output, i.e., config.status and config.log
address@hidden example
 @end itemize
 
 @cindex Known bugs in this manual or CVS
@@ -14621,7 +14648,9 @@
 whether a particular bug is a known one.  The file
 @sc{bugs} in the @sc{cvs} source distribution is one
 list of known bugs, but it doesn't necessarily try to
-be comprehensive.  Perhaps there will never be a
+be comprehensive.  A second list of known bugs exists at 
address@hidden://savannah.nongnu.org/bugs/?group=cvs&func=browse&set=open}.
+Perhaps there will never be a 
 comprehensive, detailed list of known bugs.
 
 @c ---------------------------------------------------------------------

reply via email to

[Prev in Thread] Current Thread [Next in Thread]