From: Ivan Kuten <ivan.kuten@promwad.com>
To: buildroot@busybox.net
Subject: [Buildroot] Bug reporting process?
Date: Fri, 25 Jan 2008 18:45:14 +0200 [thread overview]
Message-ID: <479A121A.4000802@promwad.com> (raw)
In-Reply-To: <1CD05B980C94AC408B37C82BBABAA3E609CEAE6D@mtsexchange.dc.multitech.prv>
Tim Barr wrote:
> What is the process for reporting or commenting on bugs? I am still
> seeing the error reported in bug buildroot 00001959 even after the
> supplied patch was applied. Thanks!
>
Commenting bugs and patches attached to the issue usually done via "Add note"
in bugtracking.
Regards,
Ivan
prev parent reply other threads:[~2008-01-25 16:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-25 15:25 [Buildroot] Bug reporting process? Tim Barr
2008-01-25 16:12 ` Darik Horn
2008-01-25 16:45 ` Ivan Kuten [this message]
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=479A121A.4000802@promwad.com \
--to=ivan.kuten@promwad.com \
--cc=buildroot@busybox.net \
/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