Recent comments posted to this site:
master
branch of gitolite today on my server, and it works fine! Updated the wiki with the commands I used to setup gitolite.
@anarcat, I have modified pre-commit-annex so if it's passed already annexed files, it'll extract their metadata.
So this can be used to add metadata to files added before you installed the hook, or if you've configured more fields to be extracted.
@Matthias, here is an example of git-annex merge updating the master branch from the synced/master branch that was pushed to it earlier:
joey@darkstar:~/tmp/test/2>git annex merge merge git-annex (merging synced/git-annex into git-annex...) ok merge synced/master Updating 7942eee..1f3422e Fast-forward new_file | 1 + 1 file changed, 1 insertion(+) create mode 120000 new_file ok
If you are having trouble with it somehow, I'd suggest filing a bug report.
You can use git annex enableremote
to change an existing remote's configuration. So this should work:
# export AWS_ACCESS_KEY_ID="newRANDOMGOBBLDEYGOOK"
# export AWS_SECRET_ACCESS_KEY="news3kr1t"
# git annex enableremote cloud
AWS_ACCESS_KEY_ID
and AWS_SECRET_ACCESS_KEY
?
it's pretty awesome to have 1TB of free storage like that out there... but for storing photos, it could be improved - I filed a few bugs on the github repo here:
https://github.com/TobiasTheViking/flickrannex/issues/created_by/anarcat?state=open
thanks!
@joeyh: This must be a misunderstanding of what I want. I use version 5.20140320. I can't find a workflow where "git annex merge" changes my master branch, it only updates the git-annex branch.
Thinking again of it after some time, I am basically fine with "git annex sync". The only thing I am uncomfortable with is that the automatic merge is pushed without review.
Hi Johnny,
I wrote a patch for googledriveannex that fixed this problem for me. First you add the google drive special remote in repo1 then you clone repo1 into repo2. In repo2 you do "git annex enableremote googldrivespecialremotename" and it should work. The problem was that the init method, that is called by git annex when a special remote is first created but also when it is enabled somewhere else, did not factor in the possibility that it had already been created. I will simultaneously submit the patch to the author of the special remote plugin but here it is for you to quickly get going: