diff options
| author |  http://sameer.sbuddhe.net/blog/ <sameerds@web> | 2013-12-01 11:55:56 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2013-12-01 11:55:56 +0000 |
| commit | bbe20ac924c86d7c5617fc870a28f222c8de331a (patch) | |
| tree | 69f0d64325d4beea2f8beba7aa065bbcf71a340e /doc | |
| parent | b402396304a81db309ee6cdf7634b5ed1206fdfc (diff) | |
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/forum/avoid_rehashing_when_converting_existing_backups_into_new_remotes.mdwn | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/forum/avoid_rehashing_when_converting_existing_backups_into_new_remotes.mdwn b/doc/forum/avoid_rehashing_when_converting_existing_backups_into_new_remotes.mdwn new file mode 100644 index 000000000..34bae17fa --- /dev/null +++ b/doc/forum/avoid_rehashing_when_converting_existing_backups_into_new_remotes.mdwn @@ -0,0 +1,3 @@ +I have two copies of a large collection of photos on two computers. I have been using rsync to keep them synchronized, but I would like to use git annex instead. I finished initializing one repo, and now its time to initialize the other repo before I can sync them up. But it seems redundant that the other repo will compute its own hashes although I know that the two contents are identical. Can't I just copy the keys and tell git annex to assume that any files seen have already been hashed? + +As a start, I cloned the .git from the first machine to the second. But that wasn't enough ... I now have an empty git-annex repo in the second machine. What else is missing? |