aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2016-06-13 12:59:59 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2016-06-13 12:59:59 -0400
commit45279bc31bad704223c1c552e811186411b7c651 (patch)
treead263bd6a5c1520e5beaf3e24e1409ffdeab1a4b
parent555e43961e2352c34ad86bceb07be279b11b656e (diff)
parent2c0207ddd3ef0e0b53c29de655135158a8969453 (diff)
Merge branch 'master' of ssh://git-annex.branchable.com
-rw-r--r--doc/forum/Fsck_by_refs_or_keys__63__.mdwn5
-rw-r--r--doc/forum/git-annex__58___getUserEntryForID__58___does_not_exist___40__no_such_user__41___/comment_2_c9474c4e925948d0cabdfe7f988e1ebe._comment15
-rw-r--r--doc/forum/v5_to_v6_upgrade_strategy.mdwn21
3 files changed, 41 insertions, 0 deletions
diff --git a/doc/forum/Fsck_by_refs_or_keys__63__.mdwn b/doc/forum/Fsck_by_refs_or_keys__63__.mdwn
new file mode 100644
index 000000000..ff2d02df2
--- /dev/null
+++ b/doc/forum/Fsck_by_refs_or_keys__63__.mdwn
@@ -0,0 +1,5 @@
+Hello,
+
+I'm trying to wrote a cronjob to fsck my git-annex bare repository on a server. My problem is that there are a lot of keys with no known copies because they were file that weren't meant to stay. So I want to only check files that are live in HEAD of master. Is there anyway to tell `git-annex fsck` to only check file that are used in some refs?
+
+Thanks.
diff --git a/doc/forum/git-annex__58___getUserEntryForID__58___does_not_exist___40__no_such_user__41___/comment_2_c9474c4e925948d0cabdfe7f988e1ebe._comment b/doc/forum/git-annex__58___getUserEntryForID__58___does_not_exist___40__no_such_user__41___/comment_2_c9474c4e925948d0cabdfe7f988e1ebe._comment
new file mode 100644
index 000000000..4db7b992d
--- /dev/null
+++ b/doc/forum/git-annex__58___getUserEntryForID__58___does_not_exist___40__no_such_user__41___/comment_2_c9474c4e925948d0cabdfe7f988e1ebe._comment
@@ -0,0 +1,15 @@
+[[!comment format=mdwn
+ username="ivan.iossifov@2673267f2e818d14a75f506d41738323cbc0bd04"
+ nickname="ivan.iossifov"
+ subject="how do I get the autobuild?"
+ date="2016-06-13T13:56:12Z"
+ content="""
+Hi Joy,
+
+Thanks a lot for the quick reply! It's seems that's exactly what will solve my problem.
+But, I couldn't find how to download the latest autobuilds.
+Would mind pointing me to it?
+
+Thanks again,
+Ivan
+"""]]
diff --git a/doc/forum/v5_to_v6_upgrade_strategy.mdwn b/doc/forum/v5_to_v6_upgrade_strategy.mdwn
new file mode 100644
index 000000000..9a34b01e3
--- /dev/null
+++ b/doc/forum/v5_to_v6_upgrade_strategy.mdwn
@@ -0,0 +1,21 @@
+I have recently jumped into git-annex, and have several TB stored in several remote annexes.
+I am able to sync to clients, and have some understanding of the operations needed to get files back etc.
+
+So far I have used v5 in Ubuntu and Debian 8. I have tried out assistant but will leave this until I better understand how git-annex works. CLI is best for this learning.
+
+I am however concerned re the upgrade path from v5 to v6. I have not been able to find a comprehensive strategy. I have tried git-annex v6 and have upgraded a client repo to v6.
+
+All of my remote repos are v5, and to be honest I am very nervous about touching them.
+
+I do have a test bed where I try out all things before doing so on my 'production' repos. So, I can play, break, redo, in safety.
+
+Any direction as to formulating a game plan for upgrading my whole network of repos, clients, etc would be very much appreciated.
+
+And, if I have missed this, a pointer would be good for sure.
+
+
+Regards,
+
+Stan
+
+While it is obvious to all: this is amazing software. Genius.