From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC] Making clear that Buildroot is no longer uClibc specific
Date: Tue, 11 Oct 2011 16:38:55 +0200 [thread overview]
Message-ID: <cover.1318343868.git.thomas.petazzoni@free-electrons.com> (raw)
Hello,
Historically, the Buildroot project was started by uClibc
developers. Nowadays, Buildroot can be used regardless of the choice
of C library, but many people still think it's an uClibc-only
solution.
Therefore, the following patch proposed to switch to a dedicated
#buildroot IRC channel instead of #uclibc.
In addition to that, it'd be great if the mailing-list had
buildroot at buildroot.org as its official address, and if the bug
tracker had http://bugs.buildroot.org as its official address.
What do you think?
Regards,
Thomas
The following changes since commit bde4564fa74cc25a088aa4173709894d2acf5844:
radvd: show it in config menu when toolchain lacks ipv6 (2011-10-11 16:10:30 +0200)
are available in the git repository at:
http://free-electrons.com/~thomas/buildroot.git for-2011.11/irc-change
Thomas Petazzoni (1):
docs: change official IRC channel to #buildroot
docs/docs.html | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
Thanks,
--
Thomas Petazzoni
next reply other threads:[~2011-10-11 14:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-11 14:38 Thomas Petazzoni [this message]
2011-10-11 14:38 ` [Buildroot] [PATCH 1/1] docs: change official IRC channel to #buildroot Thomas Petazzoni
2011-10-11 17:06 ` Yann E. MORIN
2011-10-11 18:07 ` Thomas Petazzoni
2011-10-13 15:41 ` Thomas De Schampheleire
2011-10-11 17:04 ` [Buildroot] [RFC] Making clear that Buildroot is no longer uClibc specific Yann E. MORIN
2011-10-13 15:40 ` Thomas De Schampheleire
2011-11-10 19:40 ` Thomas De Schampheleire
2011-11-11 20:49 ` Peter Korsgaard
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=cover.1318343868.git.thomas.petazzoni@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