2024-05-14 17:52:20 +00:00
|
|
|
git-remote-annex will be a program that allows push/pull/clone of a git
|
|
|
|
repository to many types of git-annex special remote.
|
2024-04-06 23:52:07 +00:00
|
|
|
|
|
|
|
This is a redesign and reimplementation of git-remote-datalad-annex.
|
|
|
|
It will be a safer implementation, will support incremental pushes, and
|
|
|
|
will be available to users who don't use datalad.
|
2024-05-10 18:41:18 +00:00
|
|
|
--[[Joey]]
|
2024-04-06 23:52:07 +00:00
|
|
|
|
2024-05-10 18:41:18 +00:00
|
|
|
---
|
2024-04-06 23:52:07 +00:00
|
|
|
|
2024-05-10 18:41:18 +00:00
|
|
|
This is implememented and working. Remaining todo list for it:
|
2024-04-25 21:01:17 +00:00
|
|
|
|
2024-05-24 21:15:31 +00:00
|
|
|
* When git clone is used with an annex:: url that is for a directory
|
|
|
|
special remote and is missing directory=, for example, it does
|
|
|
|
not display any useful error message. git fetch does, but it seems
|
|
|
|
git clone eats git-remote-annex stderr.
|
|
|
|
|
2024-05-13 18:42:25 +00:00
|
|
|
* Cloning from an annex:: url with importtree=yes doesn't work
|
|
|
|
(with or without exporttree=yes). This is because the ContentIdentifier
|
2024-05-20 17:49:45 +00:00
|
|
|
db is not populated. It should be possible to work around this.
|
2024-05-15 21:41:55 +00:00
|
|
|
|
2024-05-10 18:41:18 +00:00
|
|
|
* datalad-annex supports cloning from the web special remote,
|
|
|
|
using an url that contains the result of pushing to eg, a directory
|
|
|
|
special remote.
|
|
|
|
`datalad-annex::https://example.com?type=web&url={noquery}`
|
|
|
|
Supporting something like this would be good.
|