summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--doc/bugs/git_annex_does_nothing_useful.mdwn2
-rw-r--r--doc/bugs/lsof__47__committer_thread_loops_occassionally.mdwn2
-rw-r--r--doc/bugs/rsync_remote_shows_no_progress.mdwn1
-rw-r--r--doc/bugs/unannex_command_doesn__39__t_all_files.mdwn4
-rw-r--r--doc/bugs/watcher_commits_unlocked_files.mdwn2
5 files changed, 11 insertions, 0 deletions
diff --git a/doc/bugs/git_annex_does_nothing_useful.mdwn b/doc/bugs/git_annex_does_nothing_useful.mdwn
index 35bbb3058..be14733ed 100644
--- a/doc/bugs/git_annex_does_nothing_useful.mdwn
+++ b/doc/bugs/git_annex_does_nothing_useful.mdwn
@@ -58,3 +58,5 @@ Alright, what if I just try to get a non-existent file?
$
Alright, it didn't fail with an error, that's very strange. What is going on here?
+
+[[!meta title="v1 file is ignored"]]
diff --git a/doc/bugs/lsof__47__committer_thread_loops_occassionally.mdwn b/doc/bugs/lsof__47__committer_thread_loops_occassionally.mdwn
index eb8a0ead0..14c47e73d 100644
--- a/doc/bugs/lsof__47__committer_thread_loops_occassionally.mdwn
+++ b/doc/bugs/lsof__47__committer_thread_loops_occassionally.mdwn
@@ -47,3 +47,5 @@ Already up-to-date.
</pre>
I ran " git annex watch -d --foreground" to watch what was going one, and just created a .gitignore file and the the commiter/lsof thread just loops over and over.... I only noticed as my laptop battery had drained at somepoint when git-annex was running in the background.
+
+[[!meta title="assistant: lsof/committer thread loops occassionally"]]
diff --git a/doc/bugs/rsync_remote_shows_no_progress.mdwn b/doc/bugs/rsync_remote_shows_no_progress.mdwn
index c6d9becc1..1b7c89c12 100644
--- a/doc/bugs/rsync_remote_shows_no_progress.mdwn
+++ b/doc/bugs/rsync_remote_shows_no_progress.mdwn
@@ -10,3 +10,4 @@ git head of today, Ubuntu 12.04
Please provide any additional information below.
I looked in the source code and found some hints that the rsync progress should actually be evaluated and shown, I'm opening a bug report for this reason.
+[[!meta title="assistant: No progress bars for file uploads"]]
diff --git a/doc/bugs/unannex_command_doesn__39__t_all_files.mdwn b/doc/bugs/unannex_command_doesn__39__t_all_files.mdwn
index 8094ed918..a6500c377 100644
--- a/doc/bugs/unannex_command_doesn__39__t_all_files.mdwn
+++ b/doc/bugs/unannex_command_doesn__39__t_all_files.mdwn
@@ -24,3 +24,7 @@
> [[annex_unannex__47__uninit_should_handle_copies]] and `unannex --fast`
> added to leave contents behind in the annex, which allows handling
> copies. But needs manual cleanup later with dropunused. --[[Joey]]
+
+> This is basically a dup of [[Large unannex operations result in stale symlinks and data loss]],
+> or at least the ideas in there will also deal with this. Closing as dupe.
+> [[done]] --[[Joey]]
diff --git a/doc/bugs/watcher_commits_unlocked_files.mdwn b/doc/bugs/watcher_commits_unlocked_files.mdwn
index ef64921f1..37c79e353 100644
--- a/doc/bugs/watcher_commits_unlocked_files.mdwn
+++ b/doc/bugs/watcher_commits_unlocked_files.mdwn
@@ -26,3 +26,5 @@ Possible approaches:
events when files are moved out of the repository (well, I do, but it
just says "file moved", with no forwarding address, so I don't know
how to find the file to unlock it.
+
+[[!meta title="assistant: watcher_commits_unlocked_files"]]