diff options
| author |  spwhitton <spwhitton@web> | 2013-09-12 15:31:35 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2013-09-12 15:31:35 +0000 |
| commit | 83d932a901cfe0b1df82eb943eaec27bb08b6f31 (patch) | |
| tree | 0724e66cbbdecb10c44de3b5e298a46244653389 | |
| parent | 1625460115574c833e039d3037b120219ad42194 (diff) | |
report bug/feature request
| -rw-r--r-- | doc/bugs/gcrypt_initremote_pushes_git-annex_but_not_master.mdwn | 9 |
1 files changed, 9 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 new file mode 100644 index 000000000..cb295a5c4 --- /dev/null +++ b/doc/bugs/gcrypt_initremote_pushes_git-annex_but_not_master.mdwn @@ -0,0 +1,9 @@ +git-annex 4.20130911 on Debian Wheezy. + +Using `git annex initremote type=gcrypt` as described [here](http://git-annex.branchable.com/tips/fully_encrypted_git_repositories_with_gcrypt/) creates the repository and pushes the `git-annex` branch to it. It doesn't push `master` (or more generally: the currently checked out branch), as I have verified using `git remote show`. + +Manually pushing the branch makes `git annex sync` sync both branches with the gcrypt remote. + +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. |