mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Merge branch 'master' of ssh://git-annex.branchable.com

Browse source
This commit is contained in:
Joey Hess 2020-05-27 12:46:52 -04:00
commit a6271b1323
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
5 changed files with 49 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
doc/forum/Thank_you.mdwn Normal file
View file

@ -0,0 +1,5 @@
Dear Joey,
Thank you very much for git-annex. This is an awesome software. I'm using it every day, for music, movies, softwares, photos... Using encryption with S3 is so convenient. Moreover, it seems you put a lot of effort in its documentation. Thank you for that, too.
PS : even if I've been using gti-annex for a few years, I just discovered the --jobs parameter. It speeds up downloads and uploads **a lot**.

23
doc/forum/dropped_files_keep_coming_back.mdwn Normal file
View file

@ -0,0 +1,23 @@
I have the following setup:
A 'working' repo in the manual group, called WORKING
2 'backup' repos in the backup group, called A & B
A rclone/gdrive repo in the backup group, called GD
numfiles has been set to 3.
A and B can directly see each-other via SSH and both can contact GD
WORKING can directly connect to A, B, and GD
I work on a set of files, git annex add them and eventually do a
$ git annex sync A --content
At some point in time later (manual or chron) A does a git annex sync --content and the files end up in A, B and GD
At some later point in time, I do a git annex drop of some of the files, and after the locks are done, the files are dropped.
At yet some later point in time, after working on more files on WORKING, I do the git annex sync A --content again, and the files
that were dropped are pulled back from A. I would expect this if WORKING were a 'client' but it's manual, so it shouldn't be pulling it back
I've checked and all three of A, B, and GD have the files in question.
Thoughts?

3
doc/todo/support_disabling_git-annex___47___guard.mdwn Normal file
View file

@ -0,0 +1,3 @@
It would be nice if I could configure a git repository to be guarded against git-annex. Or even a global git config option to default to not use git-annex but only in specific repositories meant to be used with git-annex.
We've had a source code repository added with git-annex branches (repeatedly) and the user had problems with unwanted git-annex hooks installed in his checkout. I suspect that this was a user error, i.e. running git-annex in the wrong directory, but I would like to put guards into place by disabling git-annex by default and only allowing it for certain specific repos.

9
doc/todo/support_disabling_git-annex___47___guard/comment_1_0040fe8eb9df9f0a7cb7c4e490f41e6d._comment Normal file
View file

@ -0,0 +1,9 @@
[[!comment format=mdwn
username="kyle"
avatar="http://cdn.libravatar.org/avatar/7d6e85cde1422ad60607c87fa87c63f3"
subject="comment 1"
date="2020-05-27T15:19:13Z"
content="""
If you put a .noannex file in the top-level directory of a repo, `git
annex init` will refuse to initialize the repo.
"""]]

9
doc/todo/support_disabling_git-annex___47___guard/comment_2_0c3df9b8894937f2f3b4f90bee9cc096._comment Normal file
View file

@ -0,0 +1,9 @@
[[!comment format=mdwn
username="mike@2d6d71f56ce2a992244350475251df87c26fe351"
nickname="mike"
avatar="http://cdn.libravatar.org/avatar/183fa439752e2f0c6f39ede658d81050"
subject=".noannex"
date="2020-05-27T15:34:54Z"
content="""
Thanks, I didn't know about .noannex!
"""]]