generic-library/poco
1
0
Fork 0
mirror of https://github.com/pocoproject/poco.git synced 2024-12-12 10:13:51 +01:00
Code Issues Projects Releases Wiki Activity

update README.md

Browse Source
This commit is contained in:
Günter Obiltschnig 2018-03-07 17:37:57 +01:00
parent d9097c2d17
commit cffe3adcb4
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
README.md
View File

@ -1,8 +1,8 @@
![alt text][logo]
[![Travis Build Status](https://travis-ci.org/pocoproject/poco.png?branch=poco-1.9.0)](https://travis-ci.org/pocoproject/poco)
[![Build status](https://ci.appveyor.com/api/projects/status/7iyrx3f233s3akae/branch/poco-1.9.0?svg=true)](https://ci.appveyor.com/project/obiltschnig/poco/branch/poco-1.9.0)
[![Travis Build Status](https://travis-ci.org/pocoproject/poco.png?branch=poco-1.9.1)](https://travis-ci.org/pocoproject/poco)
[![Build status](https://ci.appveyor.com/api/projects/status/7iyrx3f233s3akae/branch/poco-1.9.1?svg=true)](https://ci.appveyor.com/project/obiltschnig/poco/branch/poco-1.9.1)
[![CII Best Practices](https://bestpractices.coreinfrastructure.org/projects/370/badge)](https://bestpractices.coreinfrastructure.org/projects/370)
@ -33,5 +33,5 @@ In regards to Boost, in spite of some functional overlapping,
POCO is best thought of as a Boost complement (rather than replacement).
Side-by-side use of Boost and POCO is a very common occurrence.
[overview]: https://raw.githubusercontent.com/pocoproject/poco/poco-1.9.0/doc/images/overview.png "Poco Overview"
[logo]: https://raw.githubusercontent.com/pocoproject/poco/poco-1.9.0/doc/images/logo.png "Poco Logo"
[overview]: https://raw.githubusercontent.com/pocoproject/poco/poco-1.9.1/doc/images/overview.png "Poco Overview"
[logo]: https://raw.githubusercontent.com/pocoproject/poco/poco-1.9.1/doc/images/logo.png "Poco Logo"