jstedfast / gmime / 460 / 1
70%
master: 70%

DEFAULT BRANCH: master
Ran
Files 147
Run time 5s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 70.0% (+0.05%) from 69.95%
460.1

push

travis-ci

jstedfast 
<a href="https://github.com/jstedfast/gmime/commit/<a class=hub.com/jstedfast/gmime/commit/f016b310a37ea8551e630ef5827c319f8a8f984e">f016b310a<a href="https://github.com/jstedfast/gmime/commit/f016b310a37ea8551e630ef5827c319f8a8f984e">&quot;&gt;Avoid API breakage of GMimeParserWarning (#42)

in </a><a class="double-link" href="https://github.com/jstedfast/gmime/commit/<a class="double-link" href="https://github.com/jstedfast/gmime/commit/14671817dc1a64d8840b2f612cd143f29d55ecbf">14671817d</a>">14671817d</a><a href="https://github.com/jstedfast/gmime/commit/f016b310a37ea8551e630ef5827c319f8a8f984e">,
GMIME_WARN_INVALID_PARAMETER was introduced, but it also changed the
enum values for every GMimeParserWarning that followed it in the list.

This means that if someone built against a prior version of GMime and
then upgraded their library, the library might try to return, say,
GMIME_CRIT_CONFLICTING_HEADER but the application would interpret it
as GMIME_CRIT_CONFLICTING_PARAMETER.

This change restores the original API for GMimeParserWarning, since
there is probably already released and distributed software built
against the older header files.

9856 of 14080 relevant lines covered (70.0%)

4105.83 hits per line

Source Files on job 460.1