From 4d0cc62e8ee4a950a79860077b4f4d6163c04c4c Mon Sep 17 00:00:00 2001 From: "https://id.koumbit.net/anarcat" Date: Mon, 16 Feb 2015 21:26:22 +0000 Subject: [PATCH 1/2] Added a comment --- .../comment_1_683d669ac6af8e314585609f75cfdaf3._comment | 7 +++++++ 1 file changed, 7 insertions(+) create mode 100644 doc/devblog/day_253__sqlite_for_incremental_fsck/comment_1_683d669ac6af8e314585609f75cfdaf3._comment diff --git a/doc/devblog/day_253__sqlite_for_incremental_fsck/comment_1_683d669ac6af8e314585609f75cfdaf3._comment b/doc/devblog/day_253__sqlite_for_incremental_fsck/comment_1_683d669ac6af8e314585609f75cfdaf3._comment new file mode 100644 index 0000000000..17d1d11cf2 --- /dev/null +++ b/doc/devblog/day_253__sqlite_for_incremental_fsck/comment_1_683d669ac6af8e314585609f75cfdaf3._comment @@ -0,0 +1,7 @@ +[[!comment format=mdwn + username="https://id.koumbit.net/anarcat" + subject="comment 1" + date="2015-02-16T21:26:22Z" + content=""" +i am curious: why separate database files while you can have multiple tables in the same database file? --[[anarcat]] +"""]] From 20f830cc4a9f44893070ee819b3c6b786d23ca14 Mon Sep 17 00:00:00 2001 From: "https://id.koumbit.net/anarcat" Date: Mon, 16 Feb 2015 23:22:19 +0000 Subject: [PATCH 2/2] Added a comment: watch out for direct mode --- ...omment_2_87aabff41a1c6aec773b8f52ead51105._comment | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 doc/forum/canceling_wrong_repository_merge/comment_2_87aabff41a1c6aec773b8f52ead51105._comment diff --git a/doc/forum/canceling_wrong_repository_merge/comment_2_87aabff41a1c6aec773b8f52ead51105._comment b/doc/forum/canceling_wrong_repository_merge/comment_2_87aabff41a1c6aec773b8f52ead51105._comment new file mode 100644 index 0000000000..83d5c4834a --- /dev/null +++ b/doc/forum/canceling_wrong_repository_merge/comment_2_87aabff41a1c6aec773b8f52ead51105._comment @@ -0,0 +1,11 @@ +[[!comment format=mdwn + username="https://id.koumbit.net/anarcat" + subject="watch out for direct mode" + date="2015-02-16T23:22:19Z" + content=""" +so while `git rebase` can do magic, it will not work out of the box on direct mode repositories, unless you use `-c core.bare=false`, in which case you will totally shoot yourself in the foot because git will happily remove all those real files sitting in the checkout. you will need to `git annex indirect` before you do any of that magic. working on a clone of the git repo is also a good idea, if only for testing. + +i personnally destroyed my whole music collection doing such a cleanup of the history. fortunately, i had a recent archived clone of the repo, so things weren't so bad. + +but watch out for direct mode, as always. +"""]]