From 91d1205d5529eebac27e2b7bab2b54d0c2044c1c Mon Sep 17 00:00:00 2001 From: Austin Seipp Date: Thu, 8 Feb 2024 16:49:39 -0600 Subject: [PATCH] readme: fix `[!WARNING]` section Apparently this previously-beta markdown syntax from GitHub "graduated" to a full feature in such a way that it it actually regressed in features, so doing this `[!WARNING]` inline inside of a list is no longer valid. Sigh. Scoot it up a level in the document, and just make it part of the section and not inside the list. Signed-off-by: Austin Seipp --- README.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 8e6b99373..f947cdc1a 100644 --- a/README.md +++ b/README.md @@ -93,10 +93,9 @@ And it adds several innovative, useful features of its own: well. In effect, this is a completely transparent version of `git rebase --update-refs` combined with `git rerere`, supported by design. - > [!WARNING] - > The following features are available for use, but experimental; they may - > have bugs, backwards incompatible storage changes, and user-interface - > changes! +> [!WARNING] +> The following features are available for use, but experimental; they may have +> bugs, backwards incompatible storage changes, and user-interface changes! - **Safe, concurrent replication**: Have you ever wanted to store your version controlled repositories inside a Dropbox folder? Or continuously backup