From 4b0f562a4de5bd0d33f8bab76751a89eae736caa Mon Sep 17 00:00:00 2001
From: "Joachim Wuttke (l)" <j.wuttke@fz-juelich.de>
Date: Tue, 16 Dec 2014 17:40:24 +0100
Subject: [PATCH] ..

---
 TODO | 1 -
 1 file changed, 1 deletion(-)

diff --git a/TODO b/TODO
index df32d5af..5c6dbdc5 100644
--- a/TODO
+++ b/TODO
@@ -185,4 +185,3 @@ There is another issue for your consideration: we're currently using the old yam
 We could, of course, rewrite the code to use to new API but this would be a lot of work. Luckily I have plan B.
 
 I have already a working implementation for cmake for building the old yaml-cpp as an external project for the project's internal use. The bundled old library is automatically included in the build process if yaml-cpp is missing or user specifies a -Duse_bundled_yaml_cpp=ON flag. We don't need to include the yaml-cpp sources themselves in the tree since cmake can download the directly from the web as needed. We could use this solution in the projects requiring yaml.
-
-- 
GitLab