git-annex/doc/todo/git-remote-annex.mdwn

git-remote-annex will be a program that allows push/pull/clone of a git
repository to many types of git-annex special remote.

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. 
--[[Joey]]

---

This is implememented and working. Remaining todo list for it:

* 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.

* 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.
prevent using git-remote-annex with unsuitable special remote configs I hope to support importtree=yes eventually, but it does not currently work. Added remote.<name>.allow-encrypted-gitrepo that needs to be set to allow using it with encrypted git repos. Note that even encryption=pubkey uses a cipher stored in the git repo to encrypt the keys stored in the remote. While it would be possible to not encrypt the GITBUNDLE and GITMANIFEST keys, and then allow using encryption=pubkey, it doesn't currently work, and that would be a complication that I doubt is worth it. 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.`
project we started at Distribits 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.`
preparing to merge git-remote-annex Update its todo with remaining items. Add changelog entry. Simplified internals document to no longer be notes to myself, but target users who want to understand how the data is stored and might want to extract these repos manually. Sponsored-by: Kevin Mueller on Patreon 2024-05-10 18:41:18 +00:00			`--[[Joey]]`
project we started at Distribits 2024-04-06 23:52:07 +00:00
preparing to merge git-remote-annex Update its todo with remaining items. Add changelog entry. Simplified internals document to no longer be notes to myself, but target users who want to understand how the data is stored and might want to extract these repos manually. Sponsored-by: Kevin Mueller on Patreon 2024-05-10 18:41:18 +00:00			`---`
project we started at Distribits 2024-04-06 23:52:07 +00:00
preparing to merge git-remote-annex Update its todo with remaining items. Add changelog entry. Simplified internals document to no longer be notes to myself, but target users who want to understand how the data is stored and might want to extract these repos manually. Sponsored-by: Kevin Mueller on Patreon 2024-05-10 18:41:18 +00:00			`This is implememented and working. Remaining todo list for it:`
update 2024-04-25 21:01:17 +00:00
git-remote-annex: Display full url when using remote with the shorthand url 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.`

preparing to merge git-remote-annex Update its todo with remaining items. Add changelog entry. Simplified internals document to no longer be notes to myself, but target users who want to understand how the data is stored and might want to extract these repos manually. Sponsored-by: Kevin Mueller on Patreon 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.`