From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: BTS for GRUB 2 (Re: BTS overhaul)
Date: Sun, 16 Dec 2007 12:14:54 +0100 [thread overview]
Message-ID: <20071216111454.GA7945@thorin> (raw)
In-Reply-To: <20071216110235.GA7069@thorin>
[-- Attachment #1: Type: text/plain, Size: 951 bytes --]
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
<GPLv2> I know my rights; I want my phone call!
<DRM> What use is a phone call, if you are unable to speak?
(as seen on /.)
[-- Attachment #2: bts.diff --]
[-- Type: text/x-diff, Size: 4818 bytes --]
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 @@
<link rel="stylesheet" type="text/css" href="grub.css"
media="screen" title="grub css" />
<link rel="stylesheet" type="text/css" href="print.css" media="print" />
-<title>GNU GRUB - Bug Reports</title>
+<title>GNU GRUB - GRUB 2 Bugs</title>
</head>
<body>
<div id="wrap">
@@ -47,12 +47,49 @@ media="screen" title="grub css" />
<div id="content">
<!-- end header -->
+
<h1>Bug Reports</h1>
-<p>
-GRUB 2 is under very active development, so bugs are handled in the
-developers' list <grub-devel@gnu.org> at the moment. Since this list is
-a members-only list, please subscribe to it then send e-mail to this
-list.
+
+<P>
+NOTE: For general information on how to report bugs,
+<A HREF="http://www.chiark.greenend.org.uk/~sgtatham/bugs.html">How to
+Report Bugs Effectively</A>
+is worth reading.
+</P>
+
+<P>
+When you encounter a problem or a bug, check if the
+<A HREF="http://savannah.gnu.org/bugs/?group=grub">Bug Tracking System</A>
+stores the same problem.
+Also, take a look at the <A HREF="grub-faq.en.html">GNU GRUB FAQ</A>.
+This may have a useful suggestion about your problem.
+</P>
+
+<P>
+If you didn't find information about your problem, read the chapter
+<EM>Reporting bugs</EM> in <A HREF="/software/grub/manual/">the manual</A>.
+Very often, people ask us their questions with little or even no
+information about their systems. That's quite useless, because we have
+to <EM>guess</EM> 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.
+
+</P>
+
+<P>
+Once you have realized how to write a bug report, please submit it to the
+<A HREF="http://savannah.gnu.org/bugs/?group=grub">Bug Tracking System</A>
+with information about your computer and what you did
+<EM>as much as possible</EM>. Excessive information is always better than
+no information.
+</P>
+
+<P>
+If you prefer using electronic mail, you can submit a report to the mailing
+list <bug-grub@gnu.org>.
+</P>
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" />
<h1>Bug Reports</h1>
<P>
-NOTE: For general information on how to report bugs,
-<A HREF="http://www.chiark.greenend.org.uk/~sgtatham/bugs.html">How to
-Report Bugs Effectively</A>
-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 <a href="grub-2-bugs.en.html">GRUB 2 bug</a>
+if it still applies.
</P>
<P>
-When you encounter a problem or a bug, check if the
-<A HREF="http://savannah.gnu.org/bugs/?group=grub">Bug Tracking System</A>
-stores the same problem.
-Also, take a look at the <A HREF="grub-faq.en.html">GNU GRUB FAQ</A>.
-This may have a useful suggestion about your problem.
+Additionally, if you were providing a patch please update it to work on GRUB 2.
</P>
-<P>
-If you didn't find information about your problem, read the chapter
-<EM>Reporting bugs</EM> in <A HREF="/software/grub/manual/">the manual</A>.
-Very often, people ask us their questions with little or even no
-information about their systems. That's quite useless, because we have
-to <EM>guess</EM> 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.
-
-</P>
-
-<P>
-Once you have realized how to write a bug report, please submit it to the
-<A HREF="http://savannah.gnu.org/bugs/?group=grub">Bug Tracking System</A>
-with information about your computer and what you did
-<EM>as much as possible</EM>. Excessive information is always better than
-no information.
-</P>
-
-<P>
-If you prefer using electronic mail, you can submit a report to the mailing
-list <bug-grub@gnu.org>.
-</P>
-
-
-
<!-- begin footer -->
<div class="copyright">
<p>
next prev parent reply other threads:[~2007-12-16 11:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-06 12:01 BTS overhaul Robert Millan
2007-12-12 14:37 ` Robert Millan
2007-12-12 16:43 ` Bean
2007-12-12 16:51 ` Jordi Mallach
2007-12-15 10:53 ` Robert Millan
2007-12-15 13:14 ` Marco Gerards
2007-12-16 18:36 ` Jordi Mallach
2007-12-14 22:04 ` Yoshinori K. Okuji
2007-12-15 22:43 ` BTS for GRUB 2 (Re: BTS overhaul) Robert Millan
2007-12-16 10:27 ` Vesa Jääskeläinen
2007-12-16 11:02 ` Robert Millan
2007-12-16 11:14 ` Robert Millan [this message]
2007-12-16 11:22 ` Vesa Jääskeläinen
2007-12-16 16:28 ` Robert Millan
2007-12-17 7:10 ` Yoshinori K. Okuji
2007-12-17 7:05 ` Yoshinori K. Okuji
2008-01-23 12:30 ` Marco Gerards
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071216111454.GA7945@thorin \
--to=rmh@aybabtu.com \
--cc=grub-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.