From 2cc1ec1f2b9af57742c2da7e3656b947be3d3ead Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 17 Jun 2020 18:02:43 -0400 Subject: comment --- .../comment_1_b09c0c736838132b7dd69a1c510ff877._comment | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 doc/todo/Default_of_new_style_builds_breaks_Bootstrap.OSOnly/comment_1_b09c0c736838132b7dd69a1c510ff877._comment diff --git a/doc/todo/Default_of_new_style_builds_breaks_Bootstrap.OSOnly/comment_1_b09c0c736838132b7dd69a1c510ff877._comment b/doc/todo/Default_of_new_style_builds_breaks_Bootstrap.OSOnly/comment_1_b09c0c736838132b7dd69a1c510ff877._comment new file mode 100644 index 00000000..0ca694ff --- /dev/null +++ b/doc/todo/Default_of_new_style_builds_breaks_Bootstrap.OSOnly/comment_1_b09c0c736838132b7dd69a1c510ff877._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2020-06-17T22:01:21Z" + content=""" +Simplest yes, but also kicking the can down the road as they'll +presumably remove 1- at some point. + +I've implemented new-build support in +[[!commit 745784f61bdd678e20b1b18743f18d458836a802]]. +Have not actually tested it on bootstrapping a new host yet, but I assume +it will work barring some dumb typo. +"""]] -- cgit v1.2.3