Related topics

a note on vim5 bug reporting
FiXcomTHiS.tw gnu emacs bug "Eli" == Eli Zaretskii <e...@is.elta.co.il> writes: Eli> On 21 Jan 2001, Dan Jacobson wrote: In the bug report form: This bug report will be sent to the Free Software Foundation, > not to your local site managers!! It might be polite to tell them that "it will also be plastered all over

bug report being ignored
And now a few words about the GNU bug reporting mailing lists... The GNU bug mailing lists are open and there is no expectation that bug reporters are subscribed in order to post bug reports. This makes bug reporting mailing lists fundamentally different than discussion mailing lists where everyone is expected to

Fundamental flaw in bug reporting system
It would be great if you could get Flyspray working for the weekend, it is a very good system for reporting bugs (oddly enough it seems better than the sourceforge equivalent for some reason!). I'm even more glad that none of the data seems to have been lost! If it does not go up this weekend I seem to have quite a

Kconfig: Improve init/Kconfig help ...
But seriously, I believe that bug reporting could be improved a bit by having a "Bug Central" where bugs are reported and peer-reviewed. IOW, a database server (NOT a dedicated newsgroup) where anyone with the appropriate client can submit his or her bug report. This client would ONLY be available after the user

Fundamental flaw in bug reporting system
The bug persists in SP1 and SP2. What is the best way to forward this bug to Microsoft? I know that sometimes folks in these groups will help facilitate bug reporting. Q. How can I report a SQL Server bug to Microsoft? A. There are several ways, but the >>ONLY<< way you can be sure of an engineer looking at it and

Bug#458478: closed by Julien BLACHE <jblache@debian.org> (Bug ...
René Stach r...@biba.uni-bremen.de opera tech Wojciech Eysymontt wrote: "Toman" <to...@www.com> was that kind to write: I like the new bug-reporting interface, especially the unique e-mail address to which you can send updates to your submitted bug. Nicely done! ) Ditto. :o) And the "Steps to reproduce bug" - makes

bug-reporting for non-English users
Jeff Overcash (TeamB) overc...@onramp.net borland public delphi non-technical The bug report page describes a site id as "Site ID numbers are not required for bug submission, they do help us track your bug and conduct correspondence with you. If no Site ID number is specified your bug will still be processed but

Sending a bug report with reportbug fails
David Nusinow david_nusi...@verizon.net linux debian project On Thu, Jun 29, 2006 at 11:30:33AM +0100, Ian Jackson wrote: Michael Wheatley writes ("Fundamental flaw in bug reporting system"): I would understand a steep learning curve but this is a catch 22 overhang. I am a complete newbie.

Bug#188524: marked as done (www.debian.org: Reporting page ...
You -aren't obliged to use the bug reporting format, it is provided as a guide -to the kind of information that can be useful to developers - no more. -This is a suggested format for a bug report sent to the Linux kernel mailing -list. Having a standardized bug report form makes it easier for you not to

Bug reporting to JAVASOFT sucks
zachd [ms] za...@online.microsoft.com microsoft public windowsmedia beta microsoft public windowsmedia player That is NOT an appropriate place for "bug reports". That's for Wishes. If you attempt to overload the Wish service by making it serve an inappropriate duty as a "bug report" method, you'll destroy the

How to report bugs to SCO
Specifically, are you confusing "bug reporting" meaning "a report of a bug" with "bug report" meaning "bug report in Mozilla's Bugzilla system"? probably. Mozilla is not an end-user product It certainly is for end users--you don't have to integrate it or customize it before using it to browse the web. yes.

Bug#464046: closed by Michael Mende <debian@menole.net> (Bug ...
Of course when I clicked on 'don't send', Opera immediately shut down. There is presumably, somewhere other than a general news posting, to report possible bugs - isn;t there? <URL: http://www.opera.com/support/search/supsearch.dml?index=180 > has information on bug reporting and a link to the Wizard to enter the

Bug reporting to JAVASOFT sucks
The problems with MSIE should be discussed at microsoft; the problems, bugs, bug reporting system problems at Opera should be discussed at Opera and related newsgroups. And it's not just fixing bugs: I sincerely believe the current system deters, discourages bug reporting. Notice that I did acknowledge that.

Reporting bugs in Pro 5
You want $39 for reporting a bug? That's one hell of an hourly rate. $39 for reporting a single bug is understandably over-exaggerated. Non-visible and non-accessible Opera bug report database, even for bugs that have no impact whatsoever with privacy or security. are you going to reward all of them?

EQ's policies on bug reporting
Bug reporting is uncompensated, time consuming, and often frustrating. There is no need for it to be time consuming or frustrating. Those two characteristics are a result of concious decisions by SW to keep users as uninformed as possible. As for compensation, fixing problems in a timely manner would be enough for

Suggestion for http://www.debian.org/Bugs/Reporting
See # /etc/reportbug.conf for a full listing of options. zamar@vesipeto:~$ host bugs.debian.org bugs.debian.org has address 140.211.166.43 bugs.debian.org mail is handled by 0 bugs.debian.org. By the way, is there any way to test reportbug without actually reporting a bug. (test packet foo?

DbServer:Replace() another VO2.8 SP1 bug
der...@php.net mailing www php-dev ID: 28212 Updated by: der...@php.net Reported By: i...@php.net -Status: Open +Status: Bogus Bug Type: Feature/Change Request Operating ianh$ ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=28212&edit=1.

Bug reporting - Where??
Terry Porter tjpor...@gronk.porter.net comp os linux advocacy Mark Styles went insane and wrote the following on his bedroom wall with an old crayon: What do you do when you discover a potential bug? 1/ re check to see if you can repeat the bug, and make sure it *really* is a bug. 2a/ Fix it, and email the author a

Incursion Flyspray bug report/listing down
We encounter the same error as Q176479 for SQL 6.5 DBCS insertion fail with error 2627. We've confirmed our problem with the scripts attached in Q176479. Please fix it for SQL 7.0. I don't know here is a channel for bug reporting or not. But I can't find any other free channel. I don't want to pay to report a bug.

Knode bug reporting buggy?
I am was just reporting the bug for the public good and wished to move on. There's a pothole back there, thought you would like to know. I've got to go. So, before I explore the debian bug reporting system, is there a mode for folks like me? I had to get the perlbug administrator to turn off the mail.