mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

walkthrough deep links

Browse source
This commit is contained in:
Joey Hess 2011-02-27 12:47:43 -04:00
parent 98e246b49b
commit 78fa8c1b43
2 changed files with 3 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

2
doc/bugs/add_range_argument_to___34__git_annex_dropunused__34___.mdwn
View file

@ -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 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 > 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: > specifiy multiple ranges. So:
git annex dropunused `seq 1 9` `seq 11 1845` git annex dropunused `seq 1 9` `seq 11 1845`

3
doc/bugs/git_annex_migrate_leaves_old_backend_versions_around.mdwn
View file

@ -1,7 +1,8 @@
`git annex migrate` leaves old, unlinked backend versions lying around. It `git annex migrate` leaves old, unlinked backend versions lying around. It
would be great if these were purged automatically somehow. 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 > 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 > only one file has been migrated, and the content is still used. So