From f84de2760d925651ba972415bbbcc1de3dbdde9f Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawlM_DRhi_5pJrTA0HbApHR25iAgy-NBXTY" Date: Wed, 1 Oct 2014 22:02:44 +0000 Subject: [PATCH 1/9] Added a comment --- .../comment_5_c95c8b9bd617830604500213c962fc7a._comment | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 doc/bugs/sync_does_not_preserve_timestamps/comment_5_c95c8b9bd617830604500213c962fc7a._comment diff --git a/doc/bugs/sync_does_not_preserve_timestamps/comment_5_c95c8b9bd617830604500213c962fc7a._comment b/doc/bugs/sync_does_not_preserve_timestamps/comment_5_c95c8b9bd617830604500213c962fc7a._comment new file mode 100644 index 0000000000..7632548cdf --- /dev/null +++ b/doc/bugs/sync_does_not_preserve_timestamps/comment_5_c95c8b9bd617830604500213c962fc7a._comment @@ -0,0 +1,9 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawlM_DRhi_5pJrTA0HbApHR25iAgy-NBXTY" + nickname="Tor Arne" + subject="comment 5" + date="2014-10-01T22:02:43Z" + content=""" +I was just about to start using git-annex for my data when I saw this bug report, which unfortunately is a blocker. Persisting basic metadata of files that are synced seems like a core feature of a file sync/transfer tool, so I'm really hoping this can be solved somehow :/ + +"""]] From 21da74870662839da591e652b477352030fc0528 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawlM_DRhi_5pJrTA0HbApHR25iAgy-NBXTY" Date: Wed, 1 Oct 2014 22:02:56 +0000 Subject: [PATCH 2/9] Added a comment --- .../comment_6_52842fb7828267894ce59528e7b28b31._comment | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 doc/bugs/sync_does_not_preserve_timestamps/comment_6_52842fb7828267894ce59528e7b28b31._comment diff --git a/doc/bugs/sync_does_not_preserve_timestamps/comment_6_52842fb7828267894ce59528e7b28b31._comment b/doc/bugs/sync_does_not_preserve_timestamps/comment_6_52842fb7828267894ce59528e7b28b31._comment new file mode 100644 index 0000000000..dabc403299 --- /dev/null +++ b/doc/bugs/sync_does_not_preserve_timestamps/comment_6_52842fb7828267894ce59528e7b28b31._comment @@ -0,0 +1,9 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawlM_DRhi_5pJrTA0HbApHR25iAgy-NBXTY" + nickname="Tor Arne" + subject="comment 6" + date="2014-10-01T22:02:56Z" + content=""" +I was just about to start using git-annex for my data when I saw this bug report, which unfortunately is a blocker. Persisting basic metadata of files that are synced seems like a core feature of a file sync/transfer tool, so I'm really hoping this can be solved somehow :/ + +"""]] From bc1d83daf1cea60ff89df645ad155f978ef721f6 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawlM_DRhi_5pJrTA0HbApHR25iAgy-NBXTY" Date: Wed, 1 Oct 2014 22:08:31 +0000 Subject: [PATCH 3/9] removed --- .../comment_6_52842fb7828267894ce59528e7b28b31._comment | 9 --------- 1 file changed, 9 deletions(-) delete mode 100644 doc/bugs/sync_does_not_preserve_timestamps/comment_6_52842fb7828267894ce59528e7b28b31._comment diff --git a/doc/bugs/sync_does_not_preserve_timestamps/comment_6_52842fb7828267894ce59528e7b28b31._comment b/doc/bugs/sync_does_not_preserve_timestamps/comment_6_52842fb7828267894ce59528e7b28b31._comment deleted file mode 100644 index dabc403299..0000000000 --- a/doc/bugs/sync_does_not_preserve_timestamps/comment_6_52842fb7828267894ce59528e7b28b31._comment +++ /dev/null @@ -1,9 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawlM_DRhi_5pJrTA0HbApHR25iAgy-NBXTY" - nickname="Tor Arne" - subject="comment 6" - date="2014-10-01T22:02:56Z" - content=""" -I was just about to start using git-annex for my data when I saw this bug report, which unfortunately is a blocker. Persisting basic metadata of files that are synced seems like a core feature of a file sync/transfer tool, so I'm really hoping this can be solved somehow :/ - -"""]] From 44918b9571bce94efd32fe802e445ae0c9714918 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawlM_DRhi_5pJrTA0HbApHR25iAgy-NBXTY" Date: Wed, 1 Oct 2014 22:25:24 +0000 Subject: [PATCH 4/9] Added a comment --- ...comment_1_9d7591faf99ce48b1e5753c80306ae8b._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/bugs/present_files__47__directories_are_dropped_after_a_sync/comment_1_9d7591faf99ce48b1e5753c80306ae8b._comment diff --git a/doc/bugs/present_files__47__directories_are_dropped_after_a_sync/comment_1_9d7591faf99ce48b1e5753c80306ae8b._comment b/doc/bugs/present_files__47__directories_are_dropped_after_a_sync/comment_1_9d7591faf99ce48b1e5753c80306ae8b._comment new file mode 100644 index 0000000000..bb81333545 --- /dev/null +++ b/doc/bugs/present_files__47__directories_are_dropped_after_a_sync/comment_1_9d7591faf99ce48b1e5753c80306ae8b._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawlM_DRhi_5pJrTA0HbApHR25iAgy-NBXTY" + nickname="Tor Arne" + subject="comment 1" + date="2014-10-01T22:25:24Z" + content=""" +Have you found a solution for this? This seems useful if you're only interested in a subset of files/directories on your laptop, eg, but those that are fetched (present) that you are interested you'd want to keep up to date (in sync) with other computers? + +Btw, the link to the previous discussion didnt work for me. +"""]] From e0cc2f26530b0d2c46bd681e56194c549d5469cb Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawlM_DRhi_5pJrTA0HbApHR25iAgy-NBXTY" Date: Wed, 1 Oct 2014 22:39:01 +0000 Subject: [PATCH 5/9] Added a comment --- ...mment_6_b99e00d0bc4258c4cb28b544b19ea3b8._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/bugs/sync_does_not_preserve_timestamps/comment_6_b99e00d0bc4258c4cb28b544b19ea3b8._comment diff --git a/doc/bugs/sync_does_not_preserve_timestamps/comment_6_b99e00d0bc4258c4cb28b544b19ea3b8._comment b/doc/bugs/sync_does_not_preserve_timestamps/comment_6_b99e00d0bc4258c4cb28b544b19ea3b8._comment new file mode 100644 index 0000000000..67fe255950 --- /dev/null +++ b/doc/bugs/sync_does_not_preserve_timestamps/comment_6_b99e00d0bc4258c4cb28b544b19ea3b8._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawlM_DRhi_5pJrTA0HbApHR25iAgy-NBXTY" + nickname="Tor Arne" + subject="comment 6" + date="2014-10-01T22:39:01Z" + content=""" +Isn't this what the metadata feature does though? http://git-annex.branchable.com/design/metadata/ + +With annex.genmetadata true set, it should store year and mont (but not day/time? if so why not? + +Is the missing piece of the puzzle to apply the metadata again on checkout? +"""]] From 16fd5c00c511f99580555b693d3b9f9e88a4d3f6 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawlM_DRhi_5pJrTA0HbApHR25iAgy-NBXTY" Date: Wed, 1 Oct 2014 22:43:40 +0000 Subject: [PATCH 6/9] Added a comment --- .../comment_7_04cd255a516c8520a7bc1a8fad253533._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/design/metadata/comment_7_04cd255a516c8520a7bc1a8fad253533._comment diff --git a/doc/design/metadata/comment_7_04cd255a516c8520a7bc1a8fad253533._comment b/doc/design/metadata/comment_7_04cd255a516c8520a7bc1a8fad253533._comment new file mode 100644 index 0000000000..12e5042fb9 --- /dev/null +++ b/doc/design/metadata/comment_7_04cd255a516c8520a7bc1a8fad253533._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawlM_DRhi_5pJrTA0HbApHR25iAgy-NBXTY" + nickname="Tor Arne" + subject="comment 7" + date="2014-10-01T22:43:40Z" + content=""" +I have the same question as Toby, is there a particular reason the whole timestamp is not stored? +"""]] From faf19e125382207645501ae06e91f11a1da6998c Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawlM_DRhi_5pJrTA0HbApHR25iAgy-NBXTY" Date: Wed, 1 Oct 2014 22:45:36 +0000 Subject: [PATCH 7/9] Added a comment: Can tags/metadata be used for preferred content? --- .../comment_8_0a7e55e7626f72f63966fa1e1d2cf100._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/design/metadata/comment_8_0a7e55e7626f72f63966fa1e1d2cf100._comment diff --git a/doc/design/metadata/comment_8_0a7e55e7626f72f63966fa1e1d2cf100._comment b/doc/design/metadata/comment_8_0a7e55e7626f72f63966fa1e1d2cf100._comment new file mode 100644 index 0000000000..965b1932e5 --- /dev/null +++ b/doc/design/metadata/comment_8_0a7e55e7626f72f63966fa1e1d2cf100._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawlM_DRhi_5pJrTA0HbApHR25iAgy-NBXTY" + nickname="Tor Arne" + subject="Can tags/metadata be used for preferred content?" + date="2014-10-01T22:45:36Z" + content=""" +Would love to be able to \"tag\" something as archived instead of moving it into a special folder. Coupled with a FinderSync extension on OS X Yosemite for right-click menu. This would allow me to also \"view\" the archive and bring things out of there by \"untagging\" it, if I understand the feature correctly? +"""]] From 9b7bbe334dd4e72d11ee851610bf87b03cff5021 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawlM_DRhi_5pJrTA0HbApHR25iAgy-NBXTY" Date: Wed, 1 Oct 2014 23:35:39 +0000 Subject: [PATCH 8/9] Added a comment --- ...comment_9_f0bb62c885a925e0da5ae8ce3c5e9003._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/design/metadata/comment_9_f0bb62c885a925e0da5ae8ce3c5e9003._comment diff --git a/doc/design/metadata/comment_9_f0bb62c885a925e0da5ae8ce3c5e9003._comment b/doc/design/metadata/comment_9_f0bb62c885a925e0da5ae8ce3c5e9003._comment new file mode 100644 index 0000000000..fac3bf135a --- /dev/null +++ b/doc/design/metadata/comment_9_f0bb62c885a925e0da5ae8ce3c5e9003._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawlM_DRhi_5pJrTA0HbApHR25iAgy-NBXTY" + nickname="Tor Arne" + subject="comment 9" + date="2014-10-01T23:35:39Z" + content=""" +Sorry for the noise, I see that tags _can_ be used for preferred content, excellent! + +But it seems metadata is tied to a key, not to a specific file/path. If I have 10 different files all with the same content (for some reason, say a simple txt file, Gemspec, or something), and I want to tag one of them as important, it doesn't mean they all are :o +"""]] From af3f7f1a30e8201bf2dfdeffc2c732d8ff14ab00 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Thu, 2 Oct 2014 15:23:18 +0000 Subject: [PATCH 9/9] Added a comment --- .../comment_1_ec977efd277f0644767a4fc7064e4baf._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/forum/using_git-annex_with_lightroom/comment_1_ec977efd277f0644767a4fc7064e4baf._comment diff --git a/doc/forum/using_git-annex_with_lightroom/comment_1_ec977efd277f0644767a4fc7064e4baf._comment b/doc/forum/using_git-annex_with_lightroom/comment_1_ec977efd277f0644767a4fc7064e4baf._comment new file mode 100644 index 0000000000..e7e1fa9a60 --- /dev/null +++ b/doc/forum/using_git-annex_with_lightroom/comment_1_ec977efd277f0644767a4fc7064e4baf._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.54" + subject="comment 1" + date="2014-10-02T15:23:18Z" + content=""" +There's not really a way to handle this sort of thing. I suggest that you put *.lrdata in `.gitignore` +"""]]