aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/Documentation/release-notes
AgeCommit message (Collapse)AuthorFilesLines
2022-05-21fix one year off in v0.6.4's release notesLuc Van Oostenryck1-1/+1
Bernhard Voelker noticed that the date in the release notes is one year off. Fix this. Reported-by: Bernhard Voelker <mail@bernhard-voelker.de> Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
2021-09-06Sparse v0.6.4v0.6.4Luc Van Oostenryck1-2/+2
Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
2021-09-01Add release notes for incoming v0.6.4Luc Van Oostenryck2-0/+106
Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
2020-10-18Sparse v0.6.3v0.6.3Luc Van Oostenryck1-2/+3
Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
2020-10-12Sparse v0.6.3-rc1v0.6.3-rc1Luc Van Oostenryck1-0/+1
Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
2020-10-12doc: add release notes for incoming v0.6.3Luc Van Oostenryck1-4/+54
Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
2020-08-17union-cast: teach sparse about union castsLuc Van Oostenryck1-0/+5
A cast to union type is a GCC extension similar to a compound literal just for union, using the syntax of a cast. However, sparse doesn't know about them and treats them like other casts to non-scalars. So, teach sparse about them, convert them to the corresponding compound literal and add a warning flag to enable/disable the associated warning: -W[no-]union-cast. Note: a difference between union casts and compound literals is that the union casts yield rvalues while compound literals are lvalues but this distinction is not yet done in this series. Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
2020-06-21doc: update release notesLuc Van Oostenryck1-3/+9
Update the release notes with the changes since v0.6.2-rc1. Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
2020-06-16doc: copy the old relnotes hereLuc Van Oostenryck15-0/+2731
The releases notes of the versions previously released are stored on the wiki. Copy them here too (with minimal changes in the markup), so that everything is centralized here. Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
2020-06-16doc: fix code-block formatting in v0.6.2 relnotesLuc Van Oostenryck1-1/+1
The small code example at the top was in normal text-style (which is fine) but was lacking the newline between the two statements (which is much less fine). Fix this by using a '::' instead of a ':' to trigger the literal-code-block-and-more style. Reported-by: Ramsay Jones <ramsay@ramsayjones.plus.com> Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
2020-06-14doc: reindent the sublists in the relnotesLuc Van Oostenryck1-69/+67
The html-generated version of the release notes looked terrible because the used indentation was too small. Fix this by indenting the sublists by 4 instead of 2 Reported-by: Ramsay Jones <ramsay@ramsayjones.plus.com> Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
2020-06-14doc: correct some spellingRamsay Jones1-4/+4
Signed-off-by: Ramsay Jones <ramsay@ramsayjones.plus.com> Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
2020-06-13doc: add release notes for incoming v0.6.2Luc Van Oostenryck2-0/+108
Currently, the release notes are kept on the wiki which contains nothing else but a small intro. The docs are certainly as good as this wiki to keep these release notes. So, let try this for now. Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>