From: Robert Millan <rmh@aybabtu.com>
To: grub-devel@gnu.org
Subject: BTS for GRUB 2 (Re: BTS overhaul)
Date: Sat, 15 Dec 2007 23:43:17 +0100 [thread overview]
Message-ID: <20071215224317.GA5321@thorin> (raw)
In-Reply-To: <20071206120123.GC13758@thorin>
The creature has been seized:
http://savannah.gnu.org/bugs/?group=grub
I've left the bugs that apply to documentation since we'll probably reuse
much of GRUB Legacy's and they will still apply.
Finally the BTS is usable for keeping track of GRUB 2 stuff.
Two thoughts:
- The website still prompts to send GRUB 2 queries to grub-devel,
should we adjust that to make them use the BTS?
- The BTS sends bug notifications to bug-grub. Rather than moving those
to this list, perhaps it'd be a good idea to claim bug-grub for GRUB 2
(and move GRUB Legacy queries to /dev/full), so that bug tracking (which
tends to be quite verbose) is separate and this list can be used for
general discussion more confortably.
What do you think?
--
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 /.)
next prev parent reply other threads:[~2007-12-16 4:55 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 ` Robert Millan [this message]
2007-12-16 10:27 ` BTS for GRUB 2 (Re: BTS overhaul) Vesa Jääskeläinen
2007-12-16 11:02 ` Robert Millan
2007-12-16 11:14 ` Robert Millan
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=20071215224317.GA5321@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.