From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1J3rT1-0006Fl-JQ for mharc-grub-devel@gnu.org; Sun, 16 Dec 2007 06:15:31 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1J3rSy-0006EF-Um for grub-devel@gnu.org; Sun, 16 Dec 2007 06:15:29 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1J3rSs-0006CG-I9 for grub-devel@gnu.org; Sun, 16 Dec 2007 06:15:26 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1J3rSr-0006Br-Nx for grub-devel@gnu.org; Sun, 16 Dec 2007 06:15:21 -0500 Received: from aybabtu.com ([69.60.117.155]) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1J3rSq-0007fl-R6 for grub-devel@gnu.org; Sun, 16 Dec 2007 06:15:21 -0500 Received: from [192.168.10.6] (helo=thorin) by aybabtu.com with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from ) id 1J3rSj-0003RY-Pl for grub-devel@gnu.org; Sun, 16 Dec 2007 12:15:18 +0100 Received: from rmh by thorin with local (Exim 4.63) (envelope-from ) id 1J3rSQ-00024q-GQ for grub-devel@gnu.org; Sun, 16 Dec 2007 12:14:54 +0100 Date: Sun, 16 Dec 2007 12:14:54 +0100 From: Robert Millan To: The development of GRUB 2 Message-ID: <20071216111454.GA7945@thorin> References: <20071206120123.GC13758@thorin> <20071215224317.GA5321@thorin> <4764FD77.2090609@nic.fi> <20071216110235.GA7069@thorin> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="LZvS9be/3tNcYl/X" Content-Disposition: inline In-Reply-To: <20071216110235.GA7069@thorin> Organization: free as in freedom X-Message-Flag: Worried about Outlook viruses? Switch to Thunderbird! www.mozilla.com/thunderbird X-Debbugs-No-Ack: true User-Agent: Mutt/1.5.13 (2006-08-11) X-detected-kernel: by monty-python.gnu.org: Genre and OS details not recognized. Subject: Re: BTS for GRUB 2 (Re: BTS overhaul) X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: The development of GRUB 2 List-Id: The development of GRUB 2 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Dec 2007 11:15:29 -0000 --LZvS9be/3tNcYl/X Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sun, Dec 16, 2007 at 12:02:35PM +0100, Robert Millan wrote: > > > - The website still prompts to send GRUB 2 queries to grub-devel, > > > should we adjust that to make them use the BTS? > > > > Yes. And for grub legacy users (and version info what is grub legacy) > > there should be note that these are no longer being processed or > > something like that. > > Ok then. I suggest that we move grub-legacy-bugs.en.html to > grub-2-bugs.en.html, and create a new grub-legacy-bugs.en.html prompting > reporters to try reproduce their problem in GRUB 2 (if they have a problem) > or update their patches to GRUB 2. I propose the attached patch. Don't pay much attention to the grub-2-bugs.en.html part; it's simply copiing what we had in grub-legacy-bugs.en.html with a s/Legacy/2/g in the title. -- Robert Millan I know my rights; I want my phone call! What use is a phone call, if you are unable to speak? (as seen on /.) --LZvS9be/3tNcYl/X Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="bts.diff" Index: grub-2-bugs.en.html =================================================================== RCS file: /web/grub/grub/grub-2-bugs.en.html,v retrieving revision 1.14 diff -u -p -r1.14 grub-2-bugs.en.html --- grub-2-bugs.en.html 4 Jun 2006 17:04:46 -0000 1.14 +++ grub-2-bugs.en.html 16 Dec 2007 11:12:31 -0000 @@ -8,7 +8,7 @@ -GNU GRUB - Bug Reports +GNU GRUB - GRUB 2 Bugs
@@ -47,12 +47,49 @@ media="screen" title="grub css" />
+

Bug Reports

-

-GRUB 2 is under very active development, so bugs are handled in the -developers' list at the moment. Since this list is -a members-only list, please subscribe to it then send e-mail to this -list. + +

+NOTE: For general information on how to report bugs, +How to +Report Bugs Effectively +is worth reading. +

+ +

+When you encounter a problem or a bug, check if the +Bug Tracking System +stores the same problem. +Also, take a look at the GNU GRUB FAQ. +This may have a useful suggestion about your problem. +

+ +

+If you didn't find information about your problem, read the chapter +Reporting bugs in the manual. +Very often, people ask us their questions with little or even no +information about their systems. That's quite useless, because we have +to guess what you did, what was displayed and what really +happened. Please notice that we may not see your computer directly. So, +whenever you report a bug, you must include enough information so that +we can understand what happened and even reproduce your problem in our +own machines. + +

+ +

+Once you have realized how to write a bug report, please submit it to the +Bug Tracking System +with information about your computer and what you did +as much as possible. Excessive information is always better than +no information. +

+ +

+If you prefer using electronic mail, you can submit a report to the mailing +list <bug-grub@gnu.org>. +

Index: grub-legacy-bugs.en.html =================================================================== RCS file: /web/grub/grub/grub-legacy-bugs.en.html,v retrieving revision 1.13 diff -u -p -r1.13 grub-legacy-bugs.en.html --- grub-legacy-bugs.en.html 4 Jun 2006 17:04:46 -0000 1.13 +++ grub-legacy-bugs.en.html 16 Dec 2007 11:12:31 -0000 @@ -51,48 +51,16 @@ media="screen" title="grub css" />

Bug Reports

-NOTE: For general information on how to report bugs, -How to -Report Bugs Effectively -is worth reading. +Support for filing bug reports on GRUB Legacy has been discontinued. Please, check +if you can reproduce your problem with GRUB 2, or if the feature you want is already +present in GRUB 2. Then report it as a GRUB 2 bug +if it still applies.

-When you encounter a problem or a bug, check if the -Bug Tracking System -stores the same problem. -Also, take a look at the GNU GRUB FAQ. -This may have a useful suggestion about your problem. +Additionally, if you were providing a patch please update it to work on GRUB 2.

-

-If you didn't find information about your problem, read the chapter -Reporting bugs in the manual. -Very often, people ask us their questions with little or even no -information about their systems. That's quite useless, because we have -to guess what you did, what was displayed and what really -happened. Please notice that we may not see your computer directly. So, -whenever you report a bug, you must include enough information so that -we can understand what happened and even reproduce your problem in our -own machines. - -

- -

-Once you have realized how to write a bug report, please submit it to the -Bug Tracking System -with information about your computer and what you did -as much as possible. Excessive information is always better than -no information. -

- -

-If you prefer using electronic mail, you can submit a report to the mailing -list <bug-grub@gnu.org>. -

- - -