diff options
| author |  Joey Hess <joey@kitenet.net> | 2011-02-27 12:47:43 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2011-02-27 12:47:43 -0400 |
| commit | 78fa8c1b439ef6a5ea4da04b6cff1d7174818c7e (patch) | |
| tree | e32f97ef4262a42323d4bdc51f3488a3726b8363 | |
| parent | 98e246b49b3c4fed319fe7bc1e900ba20ebfc9e1 (diff) | |
walkthrough deep links
| -rw-r--r-- | doc/bugs/add_range_argument_to___34__git_annex_dropunused__34___.mdwn | 2 | ||||
| -rw-r--r-- | doc/bugs/git_annex_migrate_leaves_old_backend_versions_around.mdwn | 3 |
2 files changed, 3 insertions, 2 deletions
diff --git a/doc/bugs/add_range_argument_to___34__git_annex_dropunused__34___.mdwn b/doc/bugs/add_range_argument_to___34__git_annex_dropunused__34___.mdwn index dc9b7acda..bbe6007a8 100644 --- a/doc/bugs/add_range_argument_to___34__git_annex_dropunused__34___.mdwn +++ b/doc/bugs/add_range_argument_to___34__git_annex_dropunused__34___.mdwn @@ -9,7 +9,7 @@ I work around this lack as I want to drop all unused files anyway by something l git annex unused | grep -o -P "^ [0-9]+" | xargs git annex dropunused > It's designed to be used with `seq`. There's an example in the -> [[walkthrough]], and of course multiple seq calls can be used to +> [[walkthrough|walkthrough/unused_data]], and of course multiple seq calls can be used to > specifiy multiple ranges. So: git annex dropunused `seq 1 9` `seq 11 1845` diff --git a/doc/bugs/git_annex_migrate_leaves_old_backend_versions_around.mdwn b/doc/bugs/git_annex_migrate_leaves_old_backend_versions_around.mdwn index fc8551ddb..e37ee06bb 100644 --- a/doc/bugs/git_annex_migrate_leaves_old_backend_versions_around.mdwn +++ b/doc/bugs/git_annex_migrate_leaves_old_backend_versions_around.mdwn @@ -1,7 +1,8 @@ `git annex migrate` leaves old, unlinked backend versions lying around. It would be great if these were purged automatically somehow. -> Yes, this is an issue mentioned in the [[walkthrough#index14h2]]. +> Yes, this is an issue mentioned in the +> [[walkthrough|walkthrough/migrating_data_to_a_new_backend]]. > > Since multiple files can point to the same content, it could be that > only one file has been migrated, and the content is still used. So |