From 9811a02b6744e63ae74804099ea26c5f37c5c815 Mon Sep 17 00:00:00 2001 From: yarikoptic Date: Fri, 9 Sep 2022 16:51:47 +0000 Subject: [PATCH 1/2] Added a comment --- .../comment_2_0c60c791513acff3910a29513f7f2f78._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/todo/not_ask_git_credentials_for_password_per_each_file/comment_2_0c60c791513acff3910a29513f7f2f78._comment diff --git a/doc/todo/not_ask_git_credentials_for_password_per_each_file/comment_2_0c60c791513acff3910a29513f7f2f78._comment b/doc/todo/not_ask_git_credentials_for_password_per_each_file/comment_2_0c60c791513acff3910a29513f7f2f78._comment new file mode 100644 index 0000000000..3ad2a1e0e7 --- /dev/null +++ b/doc/todo/not_ask_git_credentials_for_password_per_each_file/comment_2_0c60c791513acff3910a29513f7f2f78._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="yarikoptic" + avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4" + subject="comment 2" + date="2022-09-09T16:51:47Z" + content=""" +Regular git remote. IIRC Login yoh, password 123 +"""]] From 7e6b2de2c5cb5f9930c976aa7d5711a1fdcb9fae Mon Sep 17 00:00:00 2001 From: jgoerzen Date: Fri, 9 Sep 2022 17:28:06 +0000 Subject: [PATCH 2/2] --- ...thout_data_also_under_.git__47__annex__63__.mdwn | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 doc/forum/Unlocked_mode_without_data_also_under_.git__47__annex__63__.mdwn diff --git a/doc/forum/Unlocked_mode_without_data_also_under_.git__47__annex__63__.mdwn b/doc/forum/Unlocked_mode_without_data_also_under_.git__47__annex__63__.mdwn new file mode 100644 index 0000000000..b5f54fc67f --- /dev/null +++ b/doc/forum/Unlocked_mode_without_data_also_under_.git__47__annex__63__.mdwn @@ -0,0 +1,13 @@ +I'm working on setting things up for making archives on both hard drives and possibly optical media. I want them readable without needing to have Linux or git-annex, so I'm going to be using NTFS (for HDDs) and UDF (for optical). So I'm using adjust --unlocked everywhere. I don't want anything mucking with the source data; making hard links, tweaking timestamps, etc. + +Additionally, timestamps are highly relevant for me to preserve. + +Initially I thought I might be able to use the directory remote with importdirectory, but I ran into a lot of performance problems with my 150,000-file setup, as well as the bug at [[/bugs/Files_recorded_with_other_file__39__s_checksums/]]. So I'm trying to work without the special remote at all, which seems to be much more performant and, I suspect, less buggy. + +So now I'm thinking of having a repo on each drive, and rsyncing the content to it. I can easily enough exclude .git. Then I git annex add, git annex sync, and I think I've got what I need. + +The question is, why, with unlocked mode, do we have to have the files also stored in .git/annex? Of course, most (though not all) files will be hardlinked to them. But as we know, when we modify a file, it invalidates its checksum, so I'm not really seeing what this adds. + +If we didn't have to do this, I could just add git-annex to the source repo itself, secure in the notion that if I only push out from there, it will never modify anything there at all. Then I could just pull elsewhere. + +On the targets, I guess it doesn't hurt too much since it's hardlinked.