summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--doc/bugs/annex_drop_is_not___34__in_effect__34___for_load_which_was___34__addurl_--batch__34__ed_but_not_yet_committed.mdwn2
-rw-r--r--doc/bugs/annex_drop_is_not___34__in_effect__34___for_load_which_was___34__addurl_--batch__34__ed_but_not_yet_committed/comment_3_e644ef3be185a88f9471584428b32653._comment12
-rw-r--r--doc/devblog/day_387__release_day/comment_2_86262439c9056c0e06623cdf79eaf9a6._comment15
-rw-r--r--doc/forum/Is_it_possible_to_create_a_view_on_files_that___42__dont__42___have_a_field_set__63__/comment_3_cda315119bd3ccce74bc3df8dd56bf1a._comment22
-rw-r--r--doc/git-annex-view.mdwn5
5 files changed, 56 insertions, 0 deletions
diff --git a/doc/bugs/annex_drop_is_not___34__in_effect__34___for_load_which_was___34__addurl_--batch__34__ed_but_not_yet_committed.mdwn b/doc/bugs/annex_drop_is_not___34__in_effect__34___for_load_which_was___34__addurl_--batch__34__ed_but_not_yet_committed.mdwn
index 5c9f47e17..2ce7c1899 100644
--- a/doc/bugs/annex_drop_is_not___34__in_effect__34___for_load_which_was___34__addurl_--batch__34__ed_but_not_yet_committed.mdwn
+++ b/doc/bugs/annex_drop_is_not___34__in_effect__34___for_load_which_was___34__addurl_--batch__34__ed_but_not_yet_committed.mdwn
@@ -62,3 +62,5 @@ t sh
[[!meta author=yoh]]
+
+> [[done]] per comments --[[Joey]]
diff --git a/doc/bugs/annex_drop_is_not___34__in_effect__34___for_load_which_was___34__addurl_--batch__34__ed_but_not_yet_committed/comment_3_e644ef3be185a88f9471584428b32653._comment b/doc/bugs/annex_drop_is_not___34__in_effect__34___for_load_which_was___34__addurl_--batch__34__ed_but_not_yet_committed/comment_3_e644ef3be185a88f9471584428b32653._comment
new file mode 100644
index 000000000..a19a249ed
--- /dev/null
+++ b/doc/bugs/annex_drop_is_not___34__in_effect__34___for_load_which_was___34__addurl_--batch__34__ed_but_not_yet_committed/comment_3_e644ef3be185a88f9471584428b32653._comment
@@ -0,0 +1,12 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 3"""
+ date="2016-05-03T17:45:39Z"
+ content="""
+Having a unified batch process wouldn't actually help at all,
+unless it forced flushing the caches when switching between
+eg, addurl and drop commands. Which would get right back to it being
+unnecessary slow, and so negate the benefits of batching.
+
+So, I agree, this can't really be improved.
+"""]]
diff --git a/doc/devblog/day_387__release_day/comment_2_86262439c9056c0e06623cdf79eaf9a6._comment b/doc/devblog/day_387__release_day/comment_2_86262439c9056c0e06623cdf79eaf9a6._comment
new file mode 100644
index 000000000..19492995a
--- /dev/null
+++ b/doc/devblog/day_387__release_day/comment_2_86262439c9056c0e06623cdf79eaf9a6._comment
@@ -0,0 +1,15 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 2"""
+ date="2016-05-03T17:56:44Z"
+ content="""
+The exposed information is not stored in the remote. If it's stored
+anywhere, it would be in a server log, which might log an attempt
+to access an un-encrypted key filename (which typically includes the
+checksum and maybe the file's extension).
+
+So on the one hand, you don't need to do anything other than upgrade
+git-annex to recover from the problem. On the other hand, if the potential
+that a un-encrypted filename of a git-annex key having leaked into a server
+log somewhere is a problem, I don't have a solution to the problem. :-/
+"""]]
diff --git a/doc/forum/Is_it_possible_to_create_a_view_on_files_that___42__dont__42___have_a_field_set__63__/comment_3_cda315119bd3ccce74bc3df8dd56bf1a._comment b/doc/forum/Is_it_possible_to_create_a_view_on_files_that___42__dont__42___have_a_field_set__63__/comment_3_cda315119bd3ccce74bc3df8dd56bf1a._comment
new file mode 100644
index 000000000..46b724ec9
--- /dev/null
+++ b/doc/forum/Is_it_possible_to_create_a_view_on_files_that___42__dont__42___have_a_field_set__63__/comment_3_cda315119bd3ccce74bc3df8dd56bf1a._comment
@@ -0,0 +1,22 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 3"""
+ date="2016-05-03T17:48:07Z"
+ content="""
+Actually, you can do it without setting the field to a dummy value.
+
+For example, to find all files without an author metadata:
+
+ git annex find --not --metadata 'author=*'
+
+Same switches can be used with other commands, including the metadata
+command.
+
+You can also use the git-annex view command to enter a branch that only
+contains the files without metadata set:
+
+ git annex view 'author!=*'
+
+(Unfortunately, adding metadata to a file does not currently update this
+view branch.)
+"""]]
diff --git a/doc/git-annex-view.mdwn b/doc/git-annex-view.mdwn
index d8d0ce5b2..74ed5dbf7 100644
--- a/doc/git-annex-view.mdwn
+++ b/doc/git-annex-view.mdwn
@@ -31,6 +31,11 @@ For example, `/=foo` will only include files from the foo
directory in the view, while `foo/=*` will preserve the
subdirectories of the foo directory in the view.
+To enter a view containing only files that lack a given metadata
+field or tag, specify field!=value or !tag. Globs can also be used here,
+so `field!="*"` will enter a view containing only files that do not have
+the field set to any value.
+
# SEE ALSO
[[git-annex]](1)