From: Thomas De Schampheleire <patrickdepinguin@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2 of 4 v2 for-2014.05] website: remove remaining references to uclibc.org
Date: Sat, 24 May 2014 22:06:49 +0200 [thread overview]
Message-ID: <1e6e3e4e5acfcd44d44b.1400962009@argentina> (raw)
In-Reply-To: <patchbomb.1400962007@argentina>
The website still used some uclibc.org URLs which can now use buildroot.org.
Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
---
v2: no changes
docs/docs.html | 2 +-
docs/js/buildroot.js | 2 +-
docs/support.html | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
Note: the news.html page still uses bugs.uclibc.org instead of
bugs.buildroot.org, which I was hesitant to change ("you can't rewrite the
past"). However, I would like to request Peter if upcoming release
announcements could start using bugs.buildroot.org instead...
Note2: Yann's comment on this patch has been integrated in the next patch,
along with some other changes
diff --git a/docs/docs.html b/docs/docs.html
--- a/docs/docs.html
+++ b/docs/docs.html
@@ -34,7 +34,7 @@ help:</p>
<li>On the <a href="irc://freenode.net/#buildroot">Buildroot IRC
channel</a>, <code>#buildroot</code> on Freenode</li>
- <li>On our <a href="https://bugs.uclibc.org">bugtracker</a>.</li>
+ <li>On our <a href="https://bugs.buildroot.org">bugtracker</a>.</li>
<li>Through the various companies offering commercial Buildroot
support.</li>
diff --git a/docs/js/buildroot.js b/docs/js/buildroot.js
--- a/docs/js/buildroot.js
+++ b/docs/js/buildroot.js
@@ -36,7 +36,7 @@ function load_activity(feedurl, divid) {
function initialize() {
load_activity("http://rss.gmane.org/topics/excerpts/gmane.comp.lib.uclibc.buildroot", "mailing-list-activity");
- load_activity("http://git.uclibc.org/buildroot/atom/?h=master", "commit-activity");
+ load_activity("http://git.buildroot.org/buildroot/atom/?h=master", "commit-activity");
}
function google_analytics() {
diff --git a/docs/support.html b/docs/support.html
--- a/docs/support.html
+++ b/docs/support.html
@@ -37,7 +37,7 @@ list with frequently asked questions...
<h3>Bug Tracker</h3>
-If you encounter any problems while using Buildroot, you can use the <a href="https://bugs.uclibc.org/">Bug Tracker</a>
+If you encounter any problems while using Buildroot, you can use the <a href="https://bugs.buildroot.org/">Bug Tracker</a>
to post your bugs and/or participate to find solutions to existing problems.
Note: Patch are only accepted through the mailing list.
next prev parent reply other threads:[~2014-05-24 20:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-24 20:06 [Buildroot] [PATCH 0 of 4 v2 for-2014.05] website: some limited updates Thomas De Schampheleire
2014-05-24 20:06 ` [Buildroot] [PATCH 1 of 4 v2 for-2014.05] website: rework Contribute page to avoid duplication with manual Thomas De Schampheleire
2014-05-25 19:44 ` Peter Korsgaard
2014-05-24 20:06 ` Thomas De Schampheleire [this message]
2014-05-25 19:47 ` [Buildroot] [PATCH 2 of 4 v2 for-2014.05] website: remove remaining references to uclibc.org Peter Korsgaard
2014-05-24 20:06 ` [Buildroot] [PATCH 3 of 4 v2 for-2014.05] website: fix typos and HTML on support page Thomas De Schampheleire
2014-05-25 19:51 ` Peter Korsgaard
2014-05-24 20:06 ` [Buildroot] [PATCH 4 of 4 v2 for-2014.05] website: add alt-tags to images Thomas De Schampheleire
2014-05-25 19:52 ` 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=1e6e3e4e5acfcd44d44b.1400962009@argentina \
--to=patrickdepinguin@gmail.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 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.