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

Merge branch 'master' of ssh://git-annex.branchable.com

Browse source
This commit is contained in:
Joey Hess 2012-10-29 17:57:15 -04:00
commit d05083bb18
4 changed files with 43 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
doc/assistant/pairing_walkthrough/comment_2_39f1162b4d43b61e957e7497df4b9e2b._comment Normal file
View file

@ -0,0 +1,8 @@
[[!comment format=mdwn
username="http://joeyh.name/"
ip="4.152.108.194"
subject="easy peasy"
date="2012-10-29T19:09:43Z"
content="""
A headless machine is probably a server. On the same page that has the \"local computer\" link, there's a \"remote server\" link that'll get you set up.
"""]]

22
doc/bugs/GPG_passphrase_repeated_prompt.mdwn Normal file
View file

@ -0,0 +1,22 @@
#### What steps will reproduce the problem?
1. Create a new repository with a directory
2. Add files
3. Select "Store your data in the cloud" with the "Remote server" option
4. Enter host, user, directory
5. Select "Use an encrypted rsync repository on the server" (Will there be an option for unencrypted later?)
6. GPG Passphrase prompt comes up for every file
#### What is the expected output? What do you see instead?
I expect to enter a passphase once and then it will sync all files with the remote server.
Instead, it begins syncing the files to the server but prompts for a GPG passphase for every single file.
#### What version of git-annex are you using? On what operating system?
3.20121017 precompiled binary on Arch Linux
#### Please provide any additional information below.
Not sure if I'm just missing a setting for GPG, but I would think I should only need to use the web app to configure the remote server.

10
doc/forum/Using___34__sync__34___to_sink_all_branches__63__/comment_2_424b0c6fdfe87ca08f5d408b7684ab08._comment Normal file
View file

@ -0,0 +1,10 @@
[[!comment format=mdwn
username="https://www.google.com/accounts/o8/id?id=AItOawlgyVag95OnpvSzQofjyX0WjW__MOMKsl0"
nickname="Sehr"
subject="comment 2"
date="2012-10-29T18:52:59Z"
content="""
It turns out, this is even easier:
As the behavior of \"git-annex sync\" includes performing a \"git commit -a\", any pending changes in the work tree will be committed anyway. This means, that it is safe to simply checkout and sync any branch, one wants to sync.
"""]]

3
doc/todo/wishlist:_more_info_in_the_standard_commit_message_of___96__sync__96__.mdwn Normal file
View file

@ -0,0 +1,3 @@
Could you include the REPO and UUID information in the "automatic sync" commit message?
This would make troubleshooting easier. (not there was much trouble with git-annex!)