- 23 May, 2019 1 commit
-
-
Andreas Marek authored
-
- 21 May, 2019 1 commit
-
-
Andreas Marek authored
-
- 20 May, 2019 1 commit
-
-
Andreas Marek authored
-
- 18 May, 2019 1 commit
-
-
Andreas Marek authored
-
- 16 May, 2019 1 commit
-
-
Andreas Marek authored
-
- 15 May, 2019 2 commits
-
-
Andreas Marek authored
-
Andreas Marek authored
-
- 12 May, 2019 1 commit
-
-
Andreas Marek authored
-
- 10 May, 2019 2 commits
-
-
Andreas Marek authored
-
Andreas Marek authored
-
- 07 May, 2019 1 commit
-
-
Andreas Marek authored
-
- 02 May, 2019 1 commit
-
-
Andreas Marek authored
-
- 18 Apr, 2019 1 commit
-
-
Andreas Marek authored
This solves issue #66
-
- 17 Apr, 2019 1 commit
-
-
Andreas Marek authored
-
- 16 Apr, 2019 1 commit
-
-
Andreas Marek authored
-
- 07 Mar, 2019 1 commit
-
-
Andreas Marek authored
-
- 05 Mar, 2019 4 commits
-
-
Andreas Marek authored
-
Andreas Marek authored
-
Andreas Marek authored
-
Andreas Marek authored
-
- 04 Mar, 2019 1 commit
-
-
Andreas Marek authored
-
- 01 Mar, 2019 2 commits
-
-
Andreas Marek authored
-
Andreas Marek authored
-
- 27 Feb, 2019 3 commits
-
-
Andreas Marek authored
-
Andreas Marek authored
-
Andreas Marek authored
-
- 25 Feb, 2019 1 commit
-
-
Andreas Marek authored
-
- 24 Feb, 2019 1 commit
-
-
Andreas Marek authored
-
- 23 Feb, 2019 1 commit
-
-
Andreas Marek authored
-
- 22 Feb, 2019 4 commits
-
-
Andreas Marek authored
-
Andreas Marek authored
-
Andreas Marek authored
-
Andreas Marek authored
-
- 20 Feb, 2019 1 commit
-
-
Andreas Marek authored
-
- 19 Feb, 2019 1 commit
-
-
Andreas Marek authored
-
- 15 Feb, 2019 1 commit
-
-
Andreas Marek authored
-
- 07 Feb, 2019 1 commit
-
-
Andreas Marek authored
-
- 06 Feb, 2019 1 commit
-
-
Andreas Marek authored
-
- 23 Jan, 2019 2 commits
-
-
Lorenz Huedepohl authored
lfind() expects a proper comparison function where the order of the arguments does not matter. Previously it was assumed that the first argument is always a pointer to an unspecific "key" object and the second argument a pointer to an array member to compare against. However, the standard requires the two arguments to be interchangeable pointers to array-member like objects. Surfaced as musl-libc does in fact call it the other way around, compared to glibc.
-
Lorenz Huedepohl authored
-