From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Creating Buildroot bug tracker accounts
Date: Sat, 17 May 2014 11:01:47 +0200 [thread overview]
Message-ID: <20140517110147.47eeecb0@free-electrons.com> (raw)
Alexey, Anton, Aaron, Sonic, Waldemar,
Would it be possible for you to create accounts on the Buildroot bug
tracker? This would allow us to assign you bugs related to architecture
specific issues. Of course, only one person for each architecture is
sufficient:
* For ARC: Alexey and/or Anton
* For Blackfin: Aaron and/or Sonic
* For Microblaze: Waldemar
Go to https://bugs.busybox.net/, create an account, and let us know the
e-mail address with which you created the account.
Thanks a lot!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next reply other threads:[~2014-05-17 9:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-17 9:01 Thomas Petazzoni [this message]
2014-05-20 10:21 ` [Buildroot] Creating Buildroot bug tracker accounts Alexey Brodkin
2014-05-20 11:18 ` Thomas Petazzoni
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=20140517110147.47eeecb0@free-electrons.com \
--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