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

change a few last v6 references to v7

Browse source 
Since v6 is not a usable repo version any longer, it's confusing to have
documentation that refers to it.

This commit was sponsored by Peter on Patreon.
This commit is contained in:
Joey Hess 2019-07-17 11:44:57 -04:00
parent 7be690f326
commit 924e5af6b9
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
5 changed files with 6 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
doc/git-annex-adjust.mdwn
View file

@ -29,7 +29,7 @@ while inside the adjusted branch will update the adjusted branch
as necessary (eg for `--hide-missing`), and will also propagate commits
back to the original branch.
This command can only be used in a v6 git-annex repository.
This command can only be used in a v7 git-annex repository.
# OPTIONS

2
doc/git-annex-direct.mdwn
View file

@ -17,7 +17,7 @@ Note that git commands that operate on the work tree will refuse to
run in direct mode repositories. Use `git annex proxy` to safely run such
commands.
Note that the direct mode/indirect mode distinction is removed in v6
Note that the direct mode/indirect mode distinction is removed in v7
git-annex repositories. In such a repository, you can
use [[git-annex-unlock]](1) to make a file's content be directly present.
You can also use [[git-annex-adjust]](1) to enter a branch where all

2
doc/git-annex-indirect.mdwn
View file

@ -11,7 +11,7 @@ git annex indirect
Switches a repository back from direct mode to the default, indirect
mode.
Note that the direct mode/indirect mode distinction is removed in v6
Note that the direct mode/indirect mode distinction is removed in v7
git-annex repositories.
# SEE ALSO

2
doc/tips/Accessing_files_in_bare_remotes_without_git-annex.mdwn
View file

@ -1,7 +1,7 @@
git-annex is amazing for my large files backup necessities, but I am a bit scared for the long-term possibility of accessing data, without git-annex.
For this reason I have prepared a small Python tool that accesses the content of bare git-annex repositories. The tool retrieves the locations of a file, and the path to the file in the current annex. This works with the last v6 version of the git-annex format.
For this reason I have prepared a small Python tool that accesses the content of bare git-annex repositories. The tool retrieves the locations of a file, and the path to the file in the current annex. This works with the last v7 version of the git-annex format.
This is motivated by the fact that in the master branch the files are stores as links to .git/annex/objects/XX/YY/KEY/KEY (as it is correct for non-bare repos), while in the bare the files are stored in annex/objecst/ZZ/WW/KEY/KEY.

4
doc/tips/largefiles.mdwn
View file

@ -1,7 +1,7 @@
[[!meta title="annex.largefiles: configuring mixed content repositories"]]
Normally commands like `git annex add` always add files to the annex.
And when using the v6 repository mode, even `git add` and `git commit -a`
And when using the v7 repository mode, even `git add` and `git commit -a`
will add files to the annex.
Let's suppose you're developing a video game, written in C. You have
@ -12,7 +12,7 @@ possibly enormous files, but still version control them.
The annex.largefiles configuration is useful for such mixed content
repositories. It's checked by `git annex add`, by `git add` and `git commit -a`
(in v6 repositories), by `git annex import` and the assistant. It's
(in v7 repositories), by `git annex import` and the assistant. It's
also used by `git annex addurl` and `git annex importfeed` when downloading
files. When a file does not match annex.largefiles, these commands will
add its content to git instead of to the annex.