- 25 Oct, 2018 5 commits
-
-
Tomas Krizek authored -
Tomas Krizek authored
-
Tomas Krizek authored
-
Tomas Krizek authored
-
Tomas Krizek authored
-
- 21 Aug, 2018 1 commit
-
-
Štěpán Balážik authored
-
- 15 May, 2018 1 commit
-
-
Štěpán Balážik authored
-
- 14 May, 2018 2 commits
-
-
Petr Špaček authored
Also, I've found out that knot-resolver in Debian stable repos is so old that it does not make sense to test on it anymore. CI now compiles latest kresd master and does comparison on it.
-
Štěpán Balážik authored
-
- 23 Apr, 2018 1 commit
-
-
Štěpán Balážik authored
-
- 05 Mar, 2018 1 commit
-
-
Štěpán Balážik authored
-
- 22 Jan, 2018 1 commit
-
-
Petr Špaček authored
-
- 27 Nov, 2017 1 commit
-
-
Petr Špaček authored
-
- 24 Nov, 2017 1 commit
-
-
Petr Špaček authored
-
- 17 Aug, 2017 1 commit
-
-
Petr Špaček authored
Right now I'm not aware of any reason to invest into Python 2 any further.
-
- 16 Aug, 2017 1 commit
-
-
Filip Široký authored
-
- 14 Aug, 2017 1 commit
-
-
Štěpán Kotek authored
-
- 16 Jul, 2017 1 commit
-
-
Petr Špaček authored
Knot resolver's repo was renamed to /knot/knot-resolver.
-
- 04 May, 2017 2 commits
-
-
Petr Špaček authored
-
Petr Špaček authored
-
- 24 Mar, 2017 1 commit
-
-
Petr Špaček authored
We want to ensure that we not push tests which do not work on latest kresd. It would lead to breakage in kresd CI.
-
- 24 Feb, 2017 1 commit
-
-
Petr Špaček authored
-
- 21 Feb, 2017 1 commit
-
-
Petr Špaček authored
Candidate (to-be-merged) version is compared against merge base (git merge-base master..HEAD). New PEP8 or Pylint defects are show stopper. Tests results for non-modified rpl files must not change.
-
