From a546c6e6ff1a7dbecdf8a6eeecddd09cfae8cdf8 Mon Sep 17 00:00:00 2001 From: CandyAngel Date: Tue, 21 Jun 2016 08:46:50 +0000 Subject: [PATCH 1/5] Added a comment --- .../comment_1_89cfca1174ea3e50a536053e73027296._comment | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 doc/news/version_6.20160613/comment_1_89cfca1174ea3e50a536053e73027296._comment diff --git a/doc/news/version_6.20160613/comment_1_89cfca1174ea3e50a536053e73027296._comment b/doc/news/version_6.20160613/comment_1_89cfca1174ea3e50a536053e73027296._comment new file mode 100644 index 0000000000..67a0dc79d0 --- /dev/null +++ b/doc/news/version_6.20160613/comment_1_89cfca1174ea3e50a536053e73027296._comment @@ -0,0 +1,9 @@ +[[!comment format=mdwn + username="CandyAngel" + subject="comment 1" + date="2016-06-21T08:46:50Z" + content=""" + Improve SHA*E extension extraction code. + +This sounds really likely to break things like [recovering files by readding](https://git-annex.branchable.com/tips/recover_data_from_lost+found/), because the key is going to be different, despite having the same backend.. +"""]] From a59c58551118083285367d194d74b79c4f99461a Mon Sep 17 00:00:00 2001 From: Don Date: Tue, 21 Jun 2016 09:35:34 +0000 Subject: [PATCH 2/5] --- ...is_not_automatically_synced_to_local_repo.mdwn | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 doc/bugs/bare_remote_is_not_automatically_synced_to_local_repo.mdwn diff --git a/doc/bugs/bare_remote_is_not_automatically_synced_to_local_repo.mdwn b/doc/bugs/bare_remote_is_not_automatically_synced_to_local_repo.mdwn new file mode 100644 index 0000000000..459b08bcb5 --- /dev/null +++ b/doc/bugs/bare_remote_is_not_automatically_synced_to_local_repo.mdwn @@ -0,0 +1,15 @@ +### Please describe the problem. + +I have a git annex repository at `~/doc` which has a remote stored on a second drive at `/media/backup/doc.git`, which is a bare git annex repo. The webapp is run from `~/doc`. Changes are made to `/media/backup/doc.git` by syncing from other computers, but then those changes to the remote are not automatically propagated to `~/doc` by the webapp. + +The use case that lead to this situation is syncing several computers to a large hard drive on a server, utilizing a bare repo as a full backup, and then wishing to have a client repo in the home folder on the server. So other computers sync their repos to `/media/backup/doc.git` and then any changes should be propagated to `~/doc` on the server. + +Changes made to `~/doc` *are* synced to the backup repository on the backup hard drive, and those changes are almost immediately synced to the other machines by the webapp running on those respective machines. Those computers are configured to connect to `/media/backup/doc.git` on the server using SSH only (and git-annex-shell on the server), and do not use XMPP. + +### What version of git-annex are you using? On what operating system? + +The amd64 pre-built tarball, git-annex version: 6.20160613-g35dbe35, running on Ubuntu 16.04. + +### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders) + +Migrated all of my syncing to git annex about 10 months ago and haven't had any significant trouble :) From addee68cecbc4eec366329de9bd9574fc0f3be92 Mon Sep 17 00:00:00 2001 From: "christophfischer@4706e95f48874dfd46092b278315693b92ea7d23" Date: Tue, 21 Jun 2016 11:42:37 +0000 Subject: [PATCH 3/5] Added a comment: how to recursively exclude files from git-annex (.gitattributes) --- ...ent_4_b6380286f60c1cd46a82a2e90c7aa05f._comment | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 doc/tips/largefiles/comment_4_b6380286f60c1cd46a82a2e90c7aa05f._comment diff --git a/doc/tips/largefiles/comment_4_b6380286f60c1cd46a82a2e90c7aa05f._comment b/doc/tips/largefiles/comment_4_b6380286f60c1cd46a82a2e90c7aa05f._comment new file mode 100644 index 0000000000..359c01e4d2 --- /dev/null +++ b/doc/tips/largefiles/comment_4_b6380286f60c1cd46a82a2e90c7aa05f._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="christophfischer@4706e95f48874dfd46092b278315693b92ea7d23" + nickname="christophfischer" + subject="how to recursively exclude files from git-annex (.gitattributes)" + date="2016-06-21T11:42:37Z" + content=""" +Hello + +it took me some time to figure out how to exclude directories matching a specific structure within the .gitattributes file: + + **/some_dir/**/below_this_dir_is_everything_in_plane_text/**/* annex.largefiles=nothing + +Maybe it helps someone else. (In case this way is the intended way) +"""]] From bff93a77212de05db8873ad1eb11d855ad45efd1 Mon Sep 17 00:00:00 2001 From: "christophfischer@4706e95f48874dfd46092b278315693b92ea7d23" Date: Tue, 21 Jun 2016 11:42:45 +0000 Subject: [PATCH 4/5] Added a comment: how to recursively exclude files from git-annex (.gitattributes) --- ...ent_5_cf7354ecc5a3e69a0cc0d47d77e52051._comment | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 doc/tips/largefiles/comment_5_cf7354ecc5a3e69a0cc0d47d77e52051._comment diff --git a/doc/tips/largefiles/comment_5_cf7354ecc5a3e69a0cc0d47d77e52051._comment b/doc/tips/largefiles/comment_5_cf7354ecc5a3e69a0cc0d47d77e52051._comment new file mode 100644 index 0000000000..e0f8143232 --- /dev/null +++ b/doc/tips/largefiles/comment_5_cf7354ecc5a3e69a0cc0d47d77e52051._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="christophfischer@4706e95f48874dfd46092b278315693b92ea7d23" + nickname="christophfischer" + subject="how to recursively exclude files from git-annex (.gitattributes)" + date="2016-06-21T11:42:45Z" + content=""" +Hello + +it took me some time to figure out how to exclude directories matching a specific structure within the .gitattributes file: + + **/some_dir/**/below_this_dir_is_everything_in_plane_text/**/* annex.largefiles=nothing + +Maybe it helps someone else. (In case this way is the intended way) +"""]] From ae02c6a2073ee9d7740e40d18de1296ccd79e9b7 Mon Sep 17 00:00:00 2001 From: "christophfischer@4706e95f48874dfd46092b278315693b92ea7d23" Date: Tue, 21 Jun 2016 11:43:09 +0000 Subject: [PATCH 5/5] removed --- ...ent_5_cf7354ecc5a3e69a0cc0d47d77e52051._comment | 14 -------------- 1 file changed, 14 deletions(-) delete mode 100644 doc/tips/largefiles/comment_5_cf7354ecc5a3e69a0cc0d47d77e52051._comment diff --git a/doc/tips/largefiles/comment_5_cf7354ecc5a3e69a0cc0d47d77e52051._comment b/doc/tips/largefiles/comment_5_cf7354ecc5a3e69a0cc0d47d77e52051._comment deleted file mode 100644 index e0f8143232..0000000000 --- a/doc/tips/largefiles/comment_5_cf7354ecc5a3e69a0cc0d47d77e52051._comment +++ /dev/null @@ -1,14 +0,0 @@ -[[!comment format=mdwn - username="christophfischer@4706e95f48874dfd46092b278315693b92ea7d23" - nickname="christophfischer" - subject="how to recursively exclude files from git-annex (.gitattributes)" - date="2016-06-21T11:42:45Z" - content=""" -Hello - -it took me some time to figure out how to exclude directories matching a specific structure within the .gitattributes file: - - **/some_dir/**/below_this_dir_is_everything_in_plane_text/**/* annex.largefiles=nothing - -Maybe it helps someone else. (In case this way is the intended way) -"""]]