1Changes between V1.0.3 and V1.0.4 released
2
3	+ Update to use stdint and the FreeRTOS specific typedefs that were
4	  introduced in FreeRTOS V8.0.0.
5
6Changes between V1.0.2 and V1.0.3 released
7
8	+ Previously, and in line with good software engineering practice, the
9	  FreeRTOS coding standard did not permit the use of char types that were
10	  not explicitly qualified as either signed or unsigned. As a result char
11	  pointers used to reference strings required casts, as did the use of any
12	  standard string handling functions. The casts ensured compiler warnings
13	  were not generated by compilers that defaulted unqualified char types to
14	  be signed or compilers that defaulted unqualified char types to be
15	  unsigned.  As it has in later MISRA standards, this rule has now been
16	  relaxed, and unqualified char types are now permitted, but only when:
17		1) The char is used to point to a human readable text string.
18		2) The char is used to hold a single ASCII character.
19
20Changes between V1.0.1 and V1.0.2 released 14/10/2013
21
22	+ Changed double quotes (") to single quotes (') in the help string to
23	  allow the strings to be used with JSON in FreeRTOS+Nabto.
24
25Changes between V1.0.0 and V1.0.1 released 05/07/2012
26
27	+ Change the name of the structure used to map a function that implements
28	  a CLI command to the string used to call the command from
29	  xCommandLineInput to CLI_Command_Definition_t, as it was always intended
30	  to be.  A #define was added to map the old name to the new name for
31	  reasons of backward compatibility.
32
33