All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Gerards <metgerards@student.han.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Bug tracker
Date: Sun, 21 Mar 2004 18:09:40 +0100	[thread overview]
Message-ID: <87wu5egm97.fsf@marco.marco-g.com> (raw)
In-Reply-To: <200403211744.57977.okuji@enbug.org> (Yoshinori K. Okuji's message of "Sun, 21 Mar 2004 17:44:57 +0100")

"Yoshinori K. Okuji" <okuji@enbug.org> writes:

> So I think the oldest method is the best: just having a file named BUGS. 
> If you want to refer to mails related to a bug, you can write a URL of 
> the list archive. If you use YAML <http://yaml.org/> as the format, it 
> would be easy to write a helper application for it.
>
> What do you think?

That is fine for me.  Do we keep changelogs for BUGS?

--
Marco




  reply	other threads:[~2004-03-21 17:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-19 22:44 Bug tracker Marco Gerards
2004-03-21 16:44 ` Yoshinori K. Okuji
2004-03-21 17:09   ` Marco Gerards [this message]
2004-03-21 17:28     ` Yoshinori K. Okuji
2004-03-21 17:29   ` Jeroen Dekkers
  -- strict thread matches above, loose matches on Subject: below --
2011-03-26  0:07 Bug Tracker Stanley F.
2011-03-26  5:42 ` Nguyen Thai Ngoc Duy

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=87wu5egm97.fsf@marco.marco-g.com \
    --to=metgerards@student.han.nl \
    --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.