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

fix formatting of inserted news

Browse source
This commit is contained in:
Joey Hess 2019-10-23 12:01:09 -04:00
parent 940be8cd70
commit b23c87cd0f
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 23 additions and 18 deletions
Download patch file Download diff file Expand all files Collapse all files

41
doc/news/version_7.20190912.mdwn
View file

@ -1,22 +1,27 @@
News for git-annex 7.20190912:
This version of git-annex uses repository version 7 for all repositories.
Existing v5 repositories will be automatically upgraded by default.
You can prevent this, by runing: git config annex.autoupgraderepository false
A v7 repository can can have some files locked while other files are
unlocked, and all git and git-annex commands can be used on both locked and
unlocked files. It's a good idea to make sure that all users of the
repository have upgraded git-annex and upgraded their repositories
to the new version before starting to use that feature, since old
versions of git-annex will ignore the new unlocked files.
The behavior of some commands changes in an upgraded repository:
* `git add` will add files to the annex, rather than adding them directly
to the git repository. To cause some files to be added directly
to git, you can configure `annex.largefiles`. For example:
git config annex.largefiles "largerthan=100kb and not (include=*.c or include=*.h)"
* `git annex unlock` and `git annex lock` change how the pointer to
the annexed content is stored in git. If you commit the change,
that will impact all clones of the repository.
This version of git-annex uses repository version 7 for all repositories.
Existing v5 repositories will be automatically upgraded by default.
You can prevent this, by runing: git config annex.autoupgraderepository false
A v7 repository can can have some files locked while other files are
unlocked, and all git and git-annex commands can be used on both locked and
unlocked files. It's a good idea to make sure that all users of the
repository have upgraded git-annex and upgraded their repositories
to the new version before starting to use that feature, since old
versions of git-annex will ignore the new unlocked files.
The behavior of some commands changes in an upgraded repository:
* `git add` will add files to the annex, rather than adding them directly
to the git repository. To cause some files to be added directly
to git, you can configure `annex.largefiles`. For example:
git config annex.largefiles "largerthan=100kb and not (include=*.c or include=*.h)"
* `git annex unlock` and `git annex lock` change how the pointer to
the annexed content is stored in git. If you commit the change,
that will impact all clones of the repository.
git-annex 7.20190912 released with [[!toggle text="these changes"]]
[[!toggleable text="""
@ -54,4 +59,4 @@ git-annex 7.20190912 released with [[!toggle text="these changes"]]
need to use pid locking.
* A git-annex-standalone rpm is now distributed along with the standalone
tarball.
* Added standalone/rpm/rpmbuild-from-standalone-tarball script."""]]
* Added standalone/rpm/rpmbuild-from-standalone-tarball script."""]]