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

Merge branch 'master' into balanced

Browse source
This commit is contained in:
Joey Hess 2024-08-30 11:01:39 -04:00
commit d0938d730b
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
28 changed files with 541 additions and 16 deletions
Download patch file Download diff file Expand all files Collapse all files

16
doc/todo/copy__47__move_support_for_pushinsteadOf_/comment_4_34d2d12c16a829498360fbb2515a685f._comment Normal file
View file

@ -0,0 +1,16 @@
[[!comment format=mdwn
username="yarikoptic"
avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4"
subject="comment 4"
date="2024-08-29T18:35:47Z"
content="""
just ran into this again with `datalad push` which surprised me (since I do not get into it with regular `git push`), and took me a bit to figure out/find this issue.
> Unless there's some reason why you need git to pull from the http url rather than from the ssh url?
It is my pattern of working with git -- clone via public URL whenever possible (so I do not have to load/use any ssh key without necessity; could use the same URLs on public and private hosts alike) and only when needed to push, automagically push via ssh. FWIW I really love such workflow and use it not only for github but other hosting providers too!
And IMHO indeed it would make total sense for a similar separation of \"use public public/read access route regardless of having or not credentials for private/write, and use secure/authenticated route only if write/push is necessary\" for git-annex too. The utility of `insteadOf` is not allowing for such separation, but at least indeed would allow \"location-wide\" overload of using secure/authenticated even when simpler public access route possible.
Indeed adding such a feature parity with `git` might break existing setups, but I would say it should only fix a possible divergence and remove the surprise that annex is behaving differently from how git does it. IMHO it is unlikely someone had `pushInsteadOf` configured to have `git` push somewhere else (thus git-annex branch going there too) while still somehow interested to use original URL for git-annex.
"""]]

8
doc/todo/get__58___allow_for_both_--branch_and_pathspec.mdwn Normal file
View file

@ -0,0 +1,8 @@
It is desired to be able to get keys which correspond for some commit which would otherwise be not easy/undesired to checkout (too big tree, tree used actively etc) .
But it seems it is impossible to do so ATM:
```shell
yoh@typhon:/mnt/DATA/data/yoh/1076_spacetop$ git annex get --branch e6888f70ed97099f83a77d5bcf3372a9a75a2b5e^ '**/*.nii.gz'
git-annex: Can only specify one of file names, --all, --branch, --unused, --failed, --key, or --incomplete
```

8
doc/todo/migration_to_VURL_by_default/comment_1_1c0e952c2d7da41e53aab3f334de87e0._comment Normal file
View file

@ -0,0 +1,8 @@
[[!comment format=mdwn
username="matrss"
avatar="http://cdn.libravatar.org/avatar/59541f50d845e5f81aff06e88a38b9de"
subject="comment 1"
date="2024-08-28T08:47:32Z"
content="""
While a migration to VURL by default would be great, I think this issue when dealing with external special remotes should first be fixed: <https://git-annex.branchable.com/bugs/VURL_verification_failure_on_first_download/>. Right now, my datalad-cds extension does not explicitly set the URL backend, so it would break if the default was to change to VURL, but I would really like to use VURL with it if it was possible.
"""]]