From e4228d72605e2bfe69e2fd00cde864a02c6f8679 Mon Sep 17 00:00:00 2001 From: Tobias Loew Date: Wed, 9 Sep 2020 20:09:25 +0200 Subject: [PATCH 1/2] Update type_with_alignment.hpp Replaced dead link --- include/boost/type_traits/type_with_alignment.hpp | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/include/boost/type_traits/type_with_alignment.hpp b/include/boost/type_traits/type_with_alignment.hpp index e396349..85cadcd 100644 --- a/include/boost/type_traits/type_with_alignment.hpp +++ b/include/boost/type_traits/type_with_alignment.hpp @@ -120,7 +120,8 @@ template<> struct is_pod< ::boost::tt_align_ns::a128> : public true_type{}; // registers. Therefore we extend type_with_alignment<> to support // such types, however, we have to be careful to use a builtin type // whenever possible otherwise we break previously working code: -// see http://article.gmane.org/gmane.comp.lib.boost.devel/173011 +// see https://groups.google.com/g/boost-developers-archive/c/cM9xfiqkwLo +// (originally http://article.gmane.org/gmane.comp.lib.boost.devel/173011) // for an example and test case. Thus types like a8 below will // be used *only* if the existing implementation can't provide a type // with suitable alignment. This does mean however, that type_with_alignment<> From 106b442289332e85972919506130fe63711b5c38 Mon Sep 17 00:00:00 2001 From: Tobias Loew Date: Thu, 10 Sep 2020 08:38:13 +0200 Subject: [PATCH 2/2] Update type_with_alignment.hpp --- include/boost/type_traits/type_with_alignment.hpp | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/include/boost/type_traits/type_with_alignment.hpp b/include/boost/type_traits/type_with_alignment.hpp index 85cadcd..e4860f9 100644 --- a/include/boost/type_traits/type_with_alignment.hpp +++ b/include/boost/type_traits/type_with_alignment.hpp @@ -120,8 +120,7 @@ template<> struct is_pod< ::boost::tt_align_ns::a128> : public true_type{}; // registers. Therefore we extend type_with_alignment<> to support // such types, however, we have to be careful to use a builtin type // whenever possible otherwise we break previously working code: -// see https://groups.google.com/g/boost-developers-archive/c/cM9xfiqkwLo -// (originally http://article.gmane.org/gmane.comp.lib.boost.devel/173011) +// see https://lists.boost.org/Archives/boost/2014/03/212391.php // for an example and test case. Thus types like a8 below will // be used *only* if the existing implementation can't provide a type // with suitable alignment. This does mean however, that type_with_alignment<>