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

This commit is contained in:
Joey Hess 2014-05-24 14:46:13 -04:00
commit e4b0fab63d
4 changed files with 34 additions and 0 deletions

View file

@ -0,0 +1,8 @@
[[!comment format=mdwn
username="http://joeyh.name/"
ip="209.250.56.36"
subject="comment 6"
date="2014-05-23T20:20:05Z"
content="""
I tried to reproduce the assistant behaving that way, but after removing sha256sum from PATH, the assistant failed to add files and complained strenuously.
"""]]

View file

@ -0,0 +1,10 @@
[[!comment format=mdwn
username="http://joeyh.name/"
ip="209.250.56.36"
subject="comment 2"
date="2014-05-24T17:48:16Z"
content="""
I reproduced this on a debian 6.0 system. Eep that's old. Probably *was* a wget bug.
After downloading with --no-check-certificate, I tried with the wget bundled in the git-annex tarball. That works.
"""]]

View file

@ -0,0 +1,8 @@
[[!comment format=mdwn
username="https://www.google.com/accounts/o8/id?id=AItOawmZilYULa6CDEGfuagoDlesyakBgnf-dF8"
nickname="Maarten"
subject="comment 2"
date="2014-05-23T23:50:58Z"
content="""
What if the drive is destroyed? How would I re-initialize a new drive to act as a substitute for the remote that was just lost?
"""]]

View file

@ -0,0 +1,8 @@
[[!comment format=mdwn
username="http://joeyh.name/"
ip="209.250.56.36"
subject="comment 3"
date="2014-05-24T18:29:03Z"
content="""
@Maarten git clone from one of the other clones of the repository to the new drive. Also, recent versions of git-annex have a `git annex reinit` command that can be used to easily initialize a repository with the same settings as a repository that was lost.
"""]]