From ee806c1175b6dcb59fb22aaa9b23480955e7630e Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 5 Mar 2012 13:47:35 -0400 Subject: [PATCH] add news item for git-annex 3.20120230 --- doc/news/version_3.20120116.mdwn | 6 ------ doc/news/version_3.20120123.mdwn | 27 --------------------------- doc/news/version_3.20120230.mdwn | 13 +++++++++++++ 3 files changed, 13 insertions(+), 33 deletions(-) delete mode 100644 doc/news/version_3.20120116.mdwn delete mode 100644 doc/news/version_3.20120123.mdwn create mode 100644 doc/news/version_3.20120230.mdwn diff --git a/doc/news/version_3.20120116.mdwn b/doc/news/version_3.20120116.mdwn deleted file mode 100644 index 0fd07df0d5..0000000000 --- a/doc/news/version_3.20120116.mdwn +++ /dev/null @@ -1,6 +0,0 @@ -git-annex 3.20120116 released with [[!toggle text="these changes"]] -[[!toggleable text=""" - * Fix data loss bug in directory special remote, when moving a file - to the remote failed, and partially transferred content was left - behind in the directory, re-running the same move would think it - succeeded and delete the local copy."""]] \ No newline at end of file diff --git a/doc/news/version_3.20120123.mdwn b/doc/news/version_3.20120123.mdwn deleted file mode 100644 index 4eb37ef2da..0000000000 --- a/doc/news/version_3.20120123.mdwn +++ /dev/null @@ -1,27 +0,0 @@ -News for git-annex 3.20120123: - - There was a bug in the handling of directory special remotes that - could cause partial file contents to be stored in them. If you use - a directory special remote, you should fsck it, to avoid potential - data loss. - Example: git annex fsck --from mydirectory - -git-annex 3.20120123 released with [[!toggle text="these changes"]] -[[!toggleable text=""" - * fsck --from: Fscking a remote is now supported. It's done by retrieving - the contents of the specified files from the remote, and checking them, - so can be an expensive operation. Still, if the remote is a special - remote, or a git repository that you cannot run fsck in locally, it's - nice to have the ability to fsck it. - * If you have any directory special remotes, now would be a good time to - fsck them, in case you were hit by the data loss bug fixed in the - previous release! - * fsck --from remote --fast: Avoids expensive file transfers, at the - expense of not checking file size and/or contents. - * Ssh connection caching is now enabled automatically by git-annex. - Only one ssh connection is made to each host per git-annex run, which - can speed some things up a lot, as well as avoiding repeated password - prompts. Concurrent git-annex processes also share ssh connections. - Cached ssh connections are shut down when git-annex exits. - * To disable the ssh caching (if for example you have your own broader - ssh caching configuration), set annex.sshcaching=false."""]] \ No newline at end of file diff --git a/doc/news/version_3.20120230.mdwn b/doc/news/version_3.20120230.mdwn new file mode 100644 index 0000000000..52ac369e01 --- /dev/null +++ b/doc/news/version_3.20120230.mdwn @@ -0,0 +1,13 @@ +git-annex 3.20120230 released with [[!toggle text="these changes"]] +[[!toggleable text=""" + * "here" can be used to refer to the current repository, + which can read better than the old "." (which still works too). + * Directory special remotes now support chunking files written to them, + avoiding writing files larger than a specified size. + * Add progress bar display to the directory special remote. + * Add configurable hooks that are run when git-annex starts and stops + using a remote: remote.name.annex-start-command and + remote.name.annex-stop-command + * Fix a bug in symlink calculation code, that triggered in rare + cases where an annexed file is in a subdirectory that nearly + matched to the .git/annex/object/xx/yy subdirectories."""]] \ No newline at end of file