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

Merge branch 'master' of ssh://git-annex.branchable.com

Browse source
This commit is contained in:
Joey Hess 2019-04-23 12:41:38 -04:00
commit 17bd6eb917
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
3 changed files with 56 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

44
doc/bugs/importtree_not_supported_in_adb_remote.mdwn Normal file
View file

@ -0,0 +1,44 @@
### Please describe the problem.
I am following these instructions:
<https://git-annex.branchable.com/tips/android_sync_with_adb/>
but encouter this issue:
```
$ git annex initremote android type=adb androiddirectory=/sdcard/DCIM encryption=none exporttree=yes importtree=yes
initremote android
git-annex: importtree is not supported by this special remote
failed
git-annex: initremote: 1 failed
```
### What steps will reproduce the problem?
```
mkdir testAdbRemote
cd testAdbRemote
git init
git annex init
git annex initremote android type=adb androiddirectory=/sdcard/DCIM encryption=none exporttree=yes importtree=yes
```
### What version of git-annex are you using? On what operating system?
Latest conda one in Ubuntu 18.04 LTS
```
$ git annex version
git-annex version: 7.20190322-g7e5502b
build flags: Assistant Webapp Pairing S3(multipartupload)(storageclasses) WebDAV Inotify DBus DesktopNotify TorrentParser MagicMime Feeds Testsuite
dependency versions: aws-0.21.1 bloomfilter-2.0.1.0 cryptonite-0.25 DAV-1.3.3 feed-1.0.1.0 ghc-8.4.2 http-client-0.5.14 persistent-sqlite-2.9.2 torrent-10000.1.1 uuid-1.3.13 yesod-1.6.0
key/value backends: SHA256E SHA256 SHA512E SHA512 SHA224E SHA224 SHA384E SHA384 SHA3_256E SHA3_256 SHA3_512E SHA3_512 SHA3_224E SHA3_224 SHA3_384E SHA3_384 SKEIN256E SKEIN256 SKEIN512E SKEIN512 BLAKE2B256E BLAKE2B256 BLAKE2B512E BLAKE2B512 BLAKE2B160E BLAKE2B160 BLAKE2B224E BLAKE2B224 BLAKE2B384E BLAKE2B384 BLAKE2S256E BLAKE2S256 BLAKE2S160E BLAKE2S160 BLAKE2S224E BLAKE2S224 BLAKE2SP256E BLAKE2SP256 BLAKE2SP224E BLAKE2SP224 SHA1E SHA1 MD5E MD5 WORM URL
remote types: git gcrypt p2p S3 bup directory rsync web bittorrent webdav adb tahoe glacier ddar hook external
operating system: linux x86_64
supported repository versions: 5 7
upgrade supported from repository versions: 0 1 2 3 4 5 6
local repository version: 5
```
### Please provide any additional information below.
Not needed
### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
git-annex has worked wonderfully well for me in the past two years of use and having the described workflow to sync with my Android would be icing on the cake! Moreover, Joey is an awesome dev!

9
doc/forum/Feature_request__58___--quiet_for_fsck__44___import__44___etc.mdwn Normal file
View file

@ -0,0 +1,9 @@
My main use for git-annex is to manage a photo/video archive of my extended family.
I regularly use `git annex import --clean-duplicates` to clean up old copies before going through the effort of manually putting data into the global directory structure. I only care about seeing how much data was removed, i.e. `git annex import --clean-duplicates foo | grep -v 'not duplicate; skipping'`. It would be a lot nicer to suppress this natively with `--quiet`. Ideally, in this case, only files which are being deleted (i.e. destructive actions), errors, and final stats (how many files were not deleted and how many were deleted) would be printed.
Along similar lines, I don't care about everything which goes right in an `fsck`; I care about anything going wrong. A `--quiet` should print errors and final stats, nothing more.
Best,
Richard

3
doc/todo/git-annex-migrate_using_git-replace.mdwn Normal file
View file

@ -0,0 +1,3 @@
Currently, git-annex-migrate leads to content (and metadata) being stored under both old and new keys. git-annex-unused can drop the contents under the old key, but then you can't access the content if you check out an older commit. Maybe, an option can be added to migrate keys using [git-replace](https://git-scm.com/docs/git-replace) ? You'd git-replace the blob .git/annex/objects/old_key with the blob .git/annex/objects/new_key, the blob ../.git/annex/objects/old_key with the blob ../.git/annex/objects/new_key , etc. You could then also have a setting to auto-migrate non-checksum keys to checksum keys whenever the contents gets downloaded.
More generally, git-annex-replace could be implemented this way, doing what git-replace does, but for git-annex keys rather than git hashes. [[git-annex-pre-commit]] might need to be changed to implement replacement of keys added later.