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

retitle

Browse source
This commit is contained in:
Joey Hess 2012-09-16 02:05:55 -04:00
parent 0b12db64d8
commit 6d1068f160
5 changed files with 11 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
doc/bugs/git_annex_does_nothing_useful.mdwn
View file

@ -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? Alright, it didn't fail with an error, that's very strange. What is going on here?
[[!meta title="v1 file is ignored"]]

2
doc/bugs/lsof__47__committer_thread_loops_occassionally.mdwn
View file

@ -47,3 +47,5 @@ Already up-to-date.
</pre> </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. 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"]]

1
doc/bugs/rsync_remote_shows_no_progress.mdwn
View file

@ -10,3 +10,4 @@ git head of today, Ubuntu 12.04
Please provide any additional information below. 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. 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"]]

4
doc/bugs/unannex_command_doesn__39__t_all_files.mdwn
View file

@ -24,3 +24,7 @@
> [[annex_unannex__47__uninit_should_handle_copies]] and `unannex --fast` > [[annex_unannex__47__uninit_should_handle_copies]] and `unannex --fast`
> added to leave contents behind in the annex, which allows handling > added to leave contents behind in the annex, which allows handling
> copies. But needs manual cleanup later with dropunused. --[[Joey]] > 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]]

2
doc/bugs/watcher_commits_unlocked_files.mdwn
View file

@ -26,3 +26,5 @@ Possible approaches:
events when files are moved out of the repository (well, I do, but it 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 just says "file moved", with no forwarding address, so I don't know
how to find the file to unlock it. how to find the file to unlock it.
[[!meta title="assistant: watcher_commits_unlocked_files"]]