From 4cd2c980d2dd807cfb348a6c820a04de6e451add Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 1 May 2024 12:14:59 -0400 Subject: [PATCH] toc --- doc/design/balanced_preferred_content.mdwn | 2 ++ doc/design/passthrough_proxy.mdwn | 2 ++ doc/todo/proving_preferred_content_behavior.mdwn | 2 ++ doc/todo/track_free_space_in_repos_via_git-annex_branch.mdwn | 2 ++ 4 files changed, 8 insertions(+) diff --git a/doc/design/balanced_preferred_content.mdwn b/doc/design/balanced_preferred_content.mdwn index 0e2bc5d417..c69f92fd04 100644 --- a/doc/design/balanced_preferred_content.mdwn +++ b/doc/design/balanced_preferred_content.mdwn @@ -1,3 +1,5 @@ +[[!toc ]] + Say we have 2 drives and want to fill them both evenly with files, different files in each drive. Currently, preferred content cannot express that entirely: diff --git a/doc/design/passthrough_proxy.mdwn b/doc/design/passthrough_proxy.mdwn index d61db3d952..fc88648e04 100644 --- a/doc/design/passthrough_proxy.mdwn +++ b/doc/design/passthrough_proxy.mdwn @@ -1,3 +1,5 @@ +[[!toc ]] + When [[balanced_preferred_content]] is used, there may be many repositories in a location -- either a server or a cluster -- and getting any given file may need to access any of them. Configuring remotes for each repository diff --git a/doc/todo/proving_preferred_content_behavior.mdwn b/doc/todo/proving_preferred_content_behavior.mdwn index 7ab5e21445..4ad7c04187 100644 --- a/doc/todo/proving_preferred_content_behavior.mdwn +++ b/doc/todo/proving_preferred_content_behavior.mdwn @@ -1,3 +1,5 @@ +[[!toc ]] + Preferred content expressions can be complicated to write and reason about. A complex expression can involve lots of repositories that can get into different states, and needs to be written to avoid unwanted behavior. diff --git a/doc/todo/track_free_space_in_repos_via_git-annex_branch.mdwn b/doc/todo/track_free_space_in_repos_via_git-annex_branch.mdwn index aa1f421b9c..1211335f8d 100644 --- a/doc/todo/track_free_space_in_repos_via_git-annex_branch.mdwn +++ b/doc/todo/track_free_space_in_repos_via_git-annex_branch.mdwn @@ -1,3 +1,5 @@ +[[!toc ]] + If the total space available in a repository for annex objects is recorded on the git-annex branch (by the user running a command probably, or perhaps automatically), then it is possible to examine the git-annex branch and