diff options
Diffstat (limited to 'doc/special_remotes')
4 files changed, 38 insertions, 0 deletions
diff --git a/doc/special_remotes/directory/comment_6_325aac80b86588912c4fd61339ccbd0b._comment b/doc/special_remotes/directory/comment_6_325aac80b86588912c4fd61339ccbd0b._comment new file mode 100644 index 000000000..7b9d21605 --- /dev/null +++ b/doc/special_remotes/directory/comment_6_325aac80b86588912c4fd61339ccbd0b._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://nicolas-schodet.myopenid.com/" + ip="2a01:e35:8ae6:f130:1e4b:d6ff:fe78:1ddb" + subject="comment 6" + date="2013-06-26T17:52:12Z" + content=""" +I tried the suggestion on comment 4, but when I add again a remote with the same path, it gets the same repository identifier and is considered dead. Is that expected? + +My use case: I use a usb drive to transfer some large files from one git annex to another, then I use the usb drive for something else and the special remote is removed. Later I want to use the same usb drive again, but when I create the repository, it starts in the dead state. +"""]] diff --git a/doc/special_remotes/directory/comment_7_4206db69d68d9917623ce02500387021._comment b/doc/special_remotes/directory/comment_7_4206db69d68d9917623ce02500387021._comment new file mode 100644 index 000000000..b1a3b953e --- /dev/null +++ b/doc/special_remotes/directory/comment_7_4206db69d68d9917623ce02500387021._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.152.108.193" + subject="comment 7" + date="2013-06-26T18:30:39Z" + content=""" +@nicolas, I suspect you are using `git annex initremote` with the same name that you used for the now dead-and-buried remote. That causes it to be reanimated, which is not what you want. + +Since git-annex version 4.20130501, `git annex initremote` is reserved for creating new remotes, not enabling old ones, so it will refuse to do this. That's to avoid exactly this confusion. + +Using `git annex initremote` with a different remote name, and the same directory should work just fine. +"""]] diff --git a/doc/special_remotes/directory/comment_8_acd9023511fe43817718bc89430f96c3._comment b/doc/special_remotes/directory/comment_8_acd9023511fe43817718bc89430f96c3._comment new file mode 100644 index 000000000..29801fa36 --- /dev/null +++ b/doc/special_remotes/directory/comment_8_acd9023511fe43817718bc89430f96c3._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawmRFKwny4rArBaz-36xTcsJYqKIgdDaw5Q" + nickname="Andrew" + subject="comment 8" + date="2013-06-26T18:46:40Z" + content=""" +For the use case you're describing, it might be better to define the usb key as a remote set to \"manual.\" Then, you can copy over the things you want with git annex copy --to=usbkey and when you're done drop everything with git annex drop --from=usbkey and never destroy the remote. +"""]] diff --git a/doc/special_remotes/directory/comment_9_d330eb808a990bb71034613c297a265e._comment b/doc/special_remotes/directory/comment_9_d330eb808a990bb71034613c297a265e._comment new file mode 100644 index 000000000..47ac7541d --- /dev/null +++ b/doc/special_remotes/directory/comment_9_d330eb808a990bb71034613c297a265e._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://nicolas-schodet.myopenid.com/" + ip="2a01:e35:8ae6:f130:1e4b:d6ff:fe78:1ddb" + subject="comment 9" + date="2013-06-26T20:05:20Z" + content=""" +Thanks for your answers. You're right, the simplest solution for me is to never remove the remote. If my directory is lost, I realized that I can simply create an empty directory. +"""]] |