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

tweaks

Browse source
This commit is contained in:
Joey Hess 2024-05-30 13:30:10 -04:00
parent adf17f5038
commit 3a48eafce4
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 2 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

4
doc/tips/storing_a_git_repository_on_any_special_remote.mdwn
View file

@ -5,7 +5,7 @@ repository alongside the annexed files. So you can `git pull`, `git push`, and
even `git clone` from a special remote. even `git clone` from a special remote.
In order to use [[git-remote-annex]], the special remote needs to have In order to use [[git-remote-annex]], the special remote needs to have
its url set to an url starting with "annex::". its url configured to something starting with "annex::".
Special remotes are not configured with such an url by default, Special remotes are not configured with such an url by default,
but it can easily be set by using the `--with-url` parameter but it can easily be set by using the `--with-url` parameter
@ -23,7 +23,7 @@ Or you could configure it manually:
git config remote.foo.fetch '+refs/heads/*:refs/remotes/foo/*' git config remote.foo.fetch '+refs/heads/*:refs/remotes/foo/*'
Now you can `git push foo` and `git pull foo`. And commands like Now you can `git push foo` and `git pull foo`. And commands like
`git-annex sync` will also use foo as a git repository. `git-annex sync` will also use foo as a git remote.
You can even `git clone` from the special remote. To do that, you need You can even `git clone` from the special remote. To do that, you need
an url that tells git-annex all about the special remote's configuration. an url that tells git-annex all about the special remote's configuration.