git-annex (10.20230626) upstream; urgency=medium

  Many commands now quote filenames that contain unusual characters the
  same way that git does, to avoid exposing control characters to the
  terminal. The core.quotePath config can be set to false to disable this
  quoting.

 -- Joey Hess <id@joeyh.name>  Mon, 26 Jun 2023 10:38:07 -0400

git-annex (10.20220218) upstream; urgency=medium

  Transition notice: Commands like `git-annex get foo*` have changed to error
  out when some of files are not checked into the repository. To get back the
  previous behavior of silently skipping unknown files, use git config
  to set annex.skipunknown to true.

 -- Joey Hess <id@joeyh.name>  Fri, 18 Feb 2022 13:12:21 -0400

git-annex (8.20211028) upstream; urgency=medium

  This version of git-annex removes support for communicating with git-annex
  remotes that have version 6.20180312 or older installed.

 -- Joey Hess <id@joeyh.name>  Wed, 05 Jan 2022 10:09:11 -0400

git-annex (8.20200523) upstream; urgency=medium

  Transition notice: Commands like `git-annex get foo*` silently skip over
  files that are not checked into git. Since that can be surprising in many
  cases, the behavior will change to erroring out when one of the listed
  files is not checked into git. This change is planned for a git-annex
  release in early 2022. If you would like to keep the current
  behavior, use git config to set annex.skipunknown to true.

 -- Joey Hess <id@joeyh.name>  Thu, 28 May 2020 13:23:40 -0400

git-annex (8.20200226) upstream; urgency=medium
  
  This version of git-annex uses repository version 8 for all repositories.

  Existing repositories will be automatically upgraded by default.
  You can prevent this, by running: git config annex.autoupgraderepository false
 
  The upgrade process involves regenerating some sqlite databases. There are a
  couple consequences of the upgrade to keep in mind:

  * Any incremental fscks that were started in v7 won't resume where
    they left off in v8, but will instead begin again from the first file.
  * An interrupted export that was started in v7 won't resume where it left
    off after upgrade to v8; files will be re-uploaded to the export remote.
  * After the upgrade, git-annex will in some situations have to do extra
    work while it finishes populating its sqlite databases.

  Also, there are some behavior changes around adding dotfiles. While before
  git-annex add skipped adding dotfiles when operating on whole directories,
  and added dotfiles that were explicitly listed to the annex, it now adds
  dotfiles to git by default, unless annex.dotfiles is set to true.

 -- Joey Hess <id@joeyh.name>  Wed, 26 Feb 2020 17:18:16 -0400

git-annex (7.20200226) upstream; urgency=high

  There was a serious regression in gcrypt and encrypted git-lfs remotes.
  Since version 7.20200202.7, git-annex incorrectly stored content
  on those remotes without encrypting it.

  If your remotes are affected, you will want to make sure to delete
  any content that git-annex has stored on them that is not encrypted!

  One way to do so is, before upgrading to this version,
  run git-annex move --from the affected remotes. It will move
  only the content that was not encrypted.

 -- Joey Hess <id@joeyh.name>  Wed, 26 Feb 2020 17:18:16 -0400

git-annex (7.20191024) upstream; urgency=medium

  When annex.largefiles is not configured, `git add` and `git commit -a`
  add files to git, not to the annex. If you have gotten used to `git add`
  adding all files to the annex, you can get that behavior back by running:
  git config annex.largefiles anything

 -- Joey Hess <id@joeyh.name>  Thu, 24 Oct 2019 13:46:52 -0400
