From 03b16a3a2d83af9b520fa5b5bad3ba76155f594d Mon Sep 17 00:00:00 2001
From: datdenkikniet <jcdra1@gmail.com>
Date: Fri, 5 May 2023 19:20:57 +0200
Subject: Archive app_task.md

---
 book/en/archive/by_example/app_task.md | 23 +++++++++++++++++++++++
 book/en/src/by-example/app_task.md     | 23 -----------------------
 2 files changed, 23 insertions(+), 23 deletions(-)
 create mode 100644 book/en/archive/by_example/app_task.md
 delete mode 100644 book/en/src/by-example/app_task.md

(limited to 'book')

diff --git a/book/en/archive/by_example/app_task.md b/book/en/archive/by_example/app_task.md
new file mode 100644
index 0000000..b2731f6
--- /dev/null
+++ b/book/en/archive/by_example/app_task.md
@@ -0,0 +1,23 @@
+<!-- Should probably be removed -->
+
+# Defining tasks with `#[task]`
+
+Tasks, defined with `#[task]`, are the main mechanism of getting work done in RTIC.
+
+Tasks can
+
+* Be spawned (now or in the future, also by themselves)
+* Receive messages (passing messages between tasks)
+* Be prioritized, allowing preemptive multitasking
+* Optionally bind to a hardware interrupt
+
+RTIC makes a distinction between “software tasks” and “hardware tasks”.
+
+*Hardware tasks* are tasks that are bound to a specific interrupt vector in the MCU while software tasks are not.
+
+This means that if a hardware task is bound to, lets say, a UART RX interrupt, the task will be run every
+time that interrupt triggers, usually when a character is received.
+
+*Software tasks* are explicitly spawned in a task, either immediately or using the Monotonic timer mechanism. 
+
+In the coming pages we will explore both tasks and the different options available.
diff --git a/book/en/src/by-example/app_task.md b/book/en/src/by-example/app_task.md
deleted file mode 100644
index b2731f6..0000000
--- a/book/en/src/by-example/app_task.md
+++ /dev/null
@@ -1,23 +0,0 @@
-<!-- Should probably be removed -->
-
-# Defining tasks with `#[task]`
-
-Tasks, defined with `#[task]`, are the main mechanism of getting work done in RTIC.
-
-Tasks can
-
-* Be spawned (now or in the future, also by themselves)
-* Receive messages (passing messages between tasks)
-* Be prioritized, allowing preemptive multitasking
-* Optionally bind to a hardware interrupt
-
-RTIC makes a distinction between “software tasks” and “hardware tasks”.
-
-*Hardware tasks* are tasks that are bound to a specific interrupt vector in the MCU while software tasks are not.
-
-This means that if a hardware task is bound to, lets say, a UART RX interrupt, the task will be run every
-time that interrupt triggers, usually when a character is received.
-
-*Software tasks* are explicitly spawned in a task, either immediately or using the Monotonic timer mechanism. 
-
-In the coming pages we will explore both tasks and the different options available.
-- 
cgit v1.2.3