diff options
| author |  Joey Hess <joey@kitenet.net> | 2013-09-12 12:45:32 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2013-09-12 12:45:32 -0400 |
| commit | 372aac807adc6c763902e4d23a153c7457fe3367 (patch) | |
| tree | 587e10120c332b99a83e8508463e7a2bc21c672a | |
| parent | fe10a0d14b8c6152169c554fee8746972fcf33fd (diff) | |
close
| -rw-r--r-- | doc/bugs/gcrypt_initremote_pushes_git-annex_but_not_master.mdwn | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/bugs/gcrypt_initremote_pushes_git-annex_but_not_master.mdwn b/doc/bugs/gcrypt_initremote_pushes_git-annex_but_not_master.mdwn index cb295a5c4..c256778c8 100644 --- a/doc/bugs/gcrypt_initremote_pushes_git-annex_but_not_master.mdwn +++ b/doc/bugs/gcrypt_initremote_pushes_git-annex_but_not_master.mdwn @@ -7,3 +7,13 @@ Manually pushing the branch makes `git annex sync` sync both branches with the g I think that it should push the current branch upon creation of the special remote, since for at least me, the whole reason for wanting `git-remote-gcrypt` is that metadata as well as data can be stored encrypted on an SSH server. Thanks for considering this. + +> The git-annex branch is pushed by initremote because I have to push +> *something* to determine the gcrypt-id. However, this is an implementation +> detail, and not a feature of initremote. (It's more like a bug of +> git-remote-gcrypt.) +> +> `git annex sync` will always push your currently checked out branch, +> as well as the git-annex branch, no matter what `initremote` has done. +> +> [[done]] --[[Joey]] |