Yaroslav Halchenko wrote: > $> git annex init --backend=SHA1E Here's your problem. --backend only sets the backend used during the current git-annex command, not globally for the repo.
> lrwxrwxrwx 1 yoh yoh 182 Jul 5 17:09 jacobian-03.nii.gz -> > .git/annex/objects/Qz/qP/SHA256-s4690--a2083e82976b8016350752f063b6ce33f3744dc0facc2e8ece9b86eacf728267/SHA256-s4690--a2083e82976b8016350752f063b6ce33f3744dc0facc2e8ece9b86eacf728267 Note the key name here starts with SHA256, so it's not using SHA1E at all. You can configure the backend on a per-git repo basis by: git config annex.backends=SHA1E Or, better, globally by: echo '* annex.backend=SHA1E' > .gitattributes git add .gitattributes > I was interested to see how git annex would handle 'composite' extensions, > e.g. > like in this case .nii.gz, where both present "meta-information". May be it > could become aware of most common compression schemes (.gz, .bz2, etc) thus > maintaining both preceeding and compression parts of the extension? i.e. > .nii.gz in the example above. I'd rather not hardcode common extensions. I've adjusted the code so it takes up to 2 extensions, stopping if it sees an "extension" that's more than 4 characters long, because that's probably part of the filename. -- see shy jo
signature.asc
Description: Digital signature
