summaryrefslogtreecommitdiff
path: root/Upgrade.hs
Commit message (Collapse)AuthorAge
* Avoid backtraces on expected failures when built with ghc 8; only use ↵Gravatar Joey Hess2016-11-15
| | | | | | | | | | | | | backtraces for unexpected errors. ghc 8 added backtraces on uncaught errors. This is great, but git-annex was using error in many places for a error message targeted at the user, in some known problem case. A backtrace only confuses such a message, so omit it. Notably, commands like git annex drop that failed due to eg, numcopies, used to use error, so had a backtrace. This commit was sponsored by Ethan Aubin.
* When auto-upgrading a v3 remote, avoid upgrading to version 6, instead keep ↵Gravatar Joey Hess2016-10-05
| | | | | | | | | | it at version 5. Fixes a bug introduced with v6 mode that I didn't notice until now. Probably not many v3 repos left out there, and upgrading them to v6 mode is not disastrous, only a little premature. This commit was sponsored by Riku Voipio
* remove 163 lines of code without changing anything except importsGravatar Joey Hess2016-01-20
|
* Use git-annex init --version=6 to get v6 for nowGravatar Joey Hess2015-12-15
| | | | | Not ready to make it default because of the direct mode upgrade needing to all happen at once.
* add v6; keep v5 working for now and manual upgradeGravatar Joey Hess2015-12-04
| | | | | | | | | | | | Since all places where a repo is used in direct mode need to have git-annex upgraded before the repo can safely be converted to v6, the upgrade needs to be manual for now. I suppose that at some point I'll want to drop all the direct mode support code. At that point, will stop supporting v5, and will need to auto-upgrade any remaining v5 repos. If possible, I'd like to carry the direct mode support for say, a year or so, to give people plenty of time to upgrade and avoid disruption.
* update my email address and homepage urlGravatar Joey Hess2015-01-21
|
* Auto-upgrade v3 indirect repos to v5 with no changes. This also fixes a ↵Gravatar Joey Hess2013-12-29
| | | | problem when a direct mode repo was somehow set to v3 rather than v4, and so the automatic direct mode upgrade to v5 was not done.
* Bug fix: annex.version did not get set on automatic upgrade to v5 direct ↵Gravatar Joey Hess2013-11-26
| | | | mode repo, so the upgrade was performed repeatedly, slowing commands down.
* webapp: Check annex.version.Gravatar Joey Hess2013-11-17
|
* v5 for direct mode, with automatic upgradeGravatar Joey Hess2013-11-05
| | | | | This includes storing the current state of the HEAD ref, which git annex sync is going to need, but does not make sync use it.
* missed some __WINDOWS__ definesGravatar Joey Hess2013-08-04
|
* fix permission damage (thanks, Windows)Gravatar Joey Hess2013-05-11
|
* git-annex now builds on Windows (doesn't work)Gravatar Joey Hess2013-05-11
|
* where indentingGravatar Joey Hess2012-11-11
|
* tweaksGravatar Joey Hess2012-01-11
|
* renameGravatar Joey Hess2011-10-05
|
* renameGravatar Joey Hess2011-10-04
|
* factor out common importsGravatar Joey Hess2011-10-03
| | | | no code changes
* improve version checking for v3Gravatar Joey Hess2011-06-22
| | | | | | | | | Do not set annex.version whenever any command is run. Just do it in init. This ensures that, if a repo has annex.version=3, it has a git-annex branch, so we don't have to run a command every time to check for the branch. Remove the old ad-hoc logic for v0 and v1, to simplify version checking.
* stub in v2 upgradeGravatar Joey Hess2011-06-22
|
* No longer auto-upgrade to repository format 2, to avoid accidental upgrades, ↵Gravatar Joey Hess2011-03-19
| | | | etc. Use git-annex upgrade when you're ready to run this version.
* Add version command to show git-annex version as well as repository version ↵Gravatar Joey Hess2011-03-19
| | | | information.
* slways set current version in new reposGravatar Joey Hess2011-03-16
| | | | detect v1 repos that don't have a version set
* upgrade groundworkGravatar Joey Hess2011-03-16
| | | | | | pulled in old versions of functions for working with keys Wrote a parser from old key filenames to new keys.
* upgrade thoughtsGravatar Joey Hess2011-03-16
| | | | long comments :)
* increase repo versionGravatar Joey Hess2011-03-15
|
* first pass at using new keysGravatar Joey Hess2011-03-15
| | | | | | | It compiles. It sorta works. Several subcommands are FIXME marked and broken, because things that used to accept separate --backend and --key params need to be changed to accept just a --key that encodes all the key info, now that there is metadata in keys.
* use ShellParam typeGravatar Joey Hess2011-02-28
| | | | | So, I have a type checked safe handling of filenames starting with dashes, throughout the code.
* use forM_ in a few placesGravatar Joey Hess2011-01-31
|
* use mapM_Gravatar Joey Hess2011-01-31
|
* better directory handlingGravatar Joey Hess2011-01-27
| | | | | | | | | | Rename Locations functions for better consitency, and make their values more consistent too. Used </> rather than manually building paths. There are still more places that manually do so, but are tricky, due to the behavior of </> when the second FilePath is absolute. So I only changed places where it obviously was relative.
* got rid of Core moduleGravatar Joey Hess2011-01-16
| | | | Most of it was to do with managing annexed Content, so put there
* Avoid multiple calls to git ls-files when passed eg, "*".Gravatar Joey Hess2010-12-23
|
* Support upgrading from a v0 annex with nothing in it.Gravatar Joey Hess2010-12-20
|
* Fix upgrade from 0.03.Gravatar Joey Hess2010-12-13
|
* move stuff out of CoreGravatar Joey Hess2010-11-14