From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Hi, new to buildroot list... how do I submit it?
Date: Wed, 25 Mar 2009 17:35:17 +0100 [thread overview]
Message-ID: <20090325173517.660c31a1@surf> (raw)
In-Reply-To: <200903250918.04360.lsargent@txdigital.com>
Le Wed, 25 Mar 2009 09:18:04 -0500,
Lloyd Sargent <lsargent@txdigital.com> a ?crit :
> I searched the list but probably didn't use the right keywords. I
> would like to submit an addition for wxWidgets (sans GUI as we don't
> use it for our application).
>
> What is the customary form? List it all in an email? Attachment? I
> would like to avoid the ire of the community!
An entry in the bug tracker, https://bugs.uclibc.net (product
buildroot), is probably the best way. It's going to be tracked, and the
list is notified when a new bug is entered anyway.
Sincerly,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2009-03-25 16:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-25 14:18 [Buildroot] Hi, new to buildroot list... how do I submit it? Lloyd Sargent
2009-03-25 16:35 ` Thomas Petazzoni [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=20090325173517.660c31a1@surf \
--to=thomas.petazzoni@free-electrons.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