Grub Development Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: grub-devel@gnu.org
Subject: bug-grub
Date: Sat, 19 Jul 2008 16:06:42 +0200	[thread overview]
Message-ID: <20080719140642.GA23265@thorin> (raw)


Hi,

Marco and I had an interesting discussion about bug-grub today:

15:54 < marco_g> nyu: Actually, I rarely look at the BTS
15:54 < marco_g> The list is a better way to process patches, IMO.
15:55 < nyu> marco_g: bug-grub is rotting
15:55 < nyu> we should really consider a list merge
15:55 < marco_g> nyu: What do you mean?
15:55 < nyu> either that, or get rid of the BTS and bug-grub
15:55 < marco_g> nyu: I do not oppose to the latter ;-)
15:55 < nyu> marco_g: a BTS *is* useful
15:56 < marco_g> nyu: I do not see any email when people post bugs for GRUB 2, is there a way to subscribe?
15:56 < marco_g> That would make it more useful to me...
15:57 < nyu> marco_g: they go to bug-grub
15:57 < marco_g> Oh, I don't read bug-grub
15:57 < marco_g> It's for GRUB Legacy as I see it.
15:59 < nyu> marco_g: then let's dislodge GRUB Legacy from it
16:00 < marco_g> nyu: Good idea, please propose it ;-)

So this is my lazy way of I'm proposing that :-)

What does everyone think?

-- 
Robert Millan

<GPLv2> I know my rights; I want my phone call!
<DRM> What good is a phone call… if you are unable to speak?
(as seen on /.)



             reply	other threads:[~2008-07-19 14:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-19 14:06 Robert Millan [this message]
2008-07-19 15:58 ` bug-grub Gregg Levine
2008-07-19 20:05   ` bug-grub Robert Millan
2008-08-04 16:19 ` bug-grub Felix Zielcke
2008-08-04 20:54 ` bug-grub Marco Gerards
2008-08-04 21:39   ` bug-grub Robert Millan
2008-08-05  6:53     ` bug-grub Vesa Jääskeläinen

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=20080719140642.GA23265@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox