From: Thomas De Schampheleire <patrickdepinguin@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2 of 8 RFCv2 for 2014.08] manual: remove 'Events' section
Date: Tue, 12 Aug 2014 22:20:07 +0200 [thread overview]
Message-ID: <384a21645bf29946ce02.1407874807@localhost> (raw)
In-Reply-To: <patchbomb.1407874805@localhost>
The list of buildroot events is outdated, a sign that the manual is not the
best place to refer to timely things like events. The wiki page is better
suited for such information.
Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
---
docs/manual/get-involved.txt | 16 ----------------
1 files changed, 0 insertions(+), 16 deletions(-)
diff -r 00ad338df278 -r 384a21645bf2 docs/manual/get-involved.txt
--- a/docs/manual/get-involved.txt Wed Aug 06 19:48:39 2014 +0200
+++ b/docs/manual/get-involved.txt Wed Aug 06 20:28:19 2014 +0200
@@ -103,19 +103,3 @@
This page is reachable at http://elinux.org/Buildroot[].
Currently, this page is mainly used as a _todo-list_.
-
-[[events]]
-=== Events
-
-==== Buildroot Developer Days aside ELC-E 2012 (November 3-4, 2012 - Barcelona)
-
-* Event page: http://elinux.org/Buildroot:DeveloperDaysELCE2012[]
-
-==== Buildroot presentation at LSM 2012 (July 12-14, 2012 - Geneva)
-
-* Announcement: http://lists.busybox.net/pipermail/buildroot/2012-May/053845.html[]
-
-==== Buildroot Developer Days aside FOSDEM 2012 (February 3, 2012 - Brussels)
-
-* Announcement & agenda thread: http://lists.busybox.net/pipermail/buildroot/2012-January/049340.html[]
-* Report: http://lists.busybox.net/pipermail/buildroot/2012-February/050371.html[]
next prev parent reply other threads:[~2014-08-12 20:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-12 20:20 [Buildroot] [PATCH 0 of 8 RFCv2 for 2014.08] manual: restructuring and improvements Thomas De Schampheleire
2014-08-12 20:20 ` [Buildroot] [PATCH 1 of 8 RFCv2 for 2014.08] manual: high-level restructuring Thomas De Schampheleire
2014-08-12 20:20 ` Thomas De Schampheleire [this message]
2014-08-12 20:20 ` [Buildroot] [PATCH 3 of 8 RFCv2 for 2014.08] manual/getting started: rename and move 'Getting involved' section Thomas De Schampheleire
2014-08-12 20:20 ` [Buildroot] [PATCH 4 of 8 RFCv2 for 2014.08] manual/getting started: rework 'Community resources' section Thomas De Schampheleire
2014-08-12 20:20 ` [Buildroot] [PATCH 5 of 8 RFCv2 for 2014.08] manual/getting started: rework 'System requirements' section Thomas De Schampheleire
2014-08-12 20:20 ` [Buildroot] [PATCH 6 of 8 RFCv2 for 2014.08] website/download: update daily snapshot section Thomas De Schampheleire
2014-08-12 20:20 ` [Buildroot] [PATCH 7 of 8 RFCv2 for 2014.08] manual/getting started: rework 'Getting Buildroot' section Thomas De Schampheleire
2014-08-12 20:20 ` [Buildroot] [PATCH 8 of 8 RFCv2 for 2014.08] manual/getting started: rework 'Using " Thomas De Schampheleire
2014-08-15 20:52 ` [Buildroot] [PATCH 0 of 8 RFCv2 for 2014.08] manual: restructuring and improvements Samuel Martin
2014-08-17 19:13 ` 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=384a21645bf29946ce02.1407874807@localhost \
--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.