move wishlists to todo

8 files changed, 0 insertions, 128 deletions

diff --git a/doc/bugs/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates.mdwn b/doc/bugs/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates.mdwn
deleted file mode 100644
index eda17aea6..000000000
--- a/doc/bugs/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates.mdwn
+++ /dev/null
@@ -1,26 +0,0 @@
-(Hi, this is paulproteus@debian, AKA Asheesh).
-
-I've been enjoying using git-annex to archive my data.
-
-It's great that, by using git-annex and the SHA1 backend, I get a space-saving kind of deduplication through the symbolic links.
-
-I'm looking for the ability to filter files, before they get added to the annex, so that I don't add new files whose content is already in the annex.look  That would help me in terms of personal file organization.
-
-It seems there is not, so this is a wishlist bug filed so that maybe such a thing might exist. What I would really like to do is:
-
-* $ git annex add --no-add-if-already-present .
-* $ git commit -m "Slurping in some photos I found on my old laptop hard drive"
-
-And then I'd do something like:
-
-* $ git clean -f
-
-to remove the files that didn't get annexed in this run. That way, only one filename would ever point to a particular SHA1.
-
-I want this because I have copies of various of mine (photos, in particular) scattered across various hard disks. If this feature existed, I could comfortably toss them all into one git annex that grew, bit by bit, to store all of these files exactly once.
-
-(I would be even happier for "git annex add --unlink-duplicates .")
-
-(Another way to do this would be to "git annex add" them all, and then use a "git annex remove-duplicates" that could prompt me about which files are duplicates of each other, and then I could pipe that command's output into xargs git rm.)
-
-(As I write this, I realize it's possible to parse the destination of the symlink in a way that does this..)
diff --git a/doc/bugs/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates/comment_1_fd213310ee548d8726791d2b02237fde._comment b/doc/bugs/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates/comment_1_fd213310ee548d8726791d2b02237fde._comment
deleted file mode 100644
index 094e4526e..000000000
--- a/doc/bugs/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates/comment_1_fd213310ee548d8726791d2b02237fde._comment
+++ /dev/null
@@ -1,29 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 1"
- date="2011-01-27T18:29:44Z"
- content="""
-Hey Asheesh, I'm happy you're finding git-annex useful.
-
-So, there are two forms of duplication going on here. There's duplication of the content, and duplication of the filenames 
-pointing at that content.
-
-Duplication of the filenames is probably not a concern, although it's what I thought you were talking about at first. It's probably info worth recording that backup-2010/some_dir/foo and backup-2009/other_dir/foo are two names you've used for the same content in the past. If you really wanted to remove backup-2009/foo, you could do it by writing a script that looks at the basenames of the symlink targets and removes files that point to the same content as other files.
-
-Using SHA1 ensures that the same key is used for identical files, so generally avoids duplication of content. But if you have 2 disks with an identical file on each, and make them both into annexes, then git-annex will happily retain both
-copies of the content, one per disk. It generally considers keeping copies of content a good thing. :)
-
-So, what if you want to remove the unnecessary copies? Well, there's a really simple way:
-
-<pre>
-cd /media/usb-1
-git remote add other-disk /media/usb-0
-git annex add
-git annex drop
-</pre>
-
-This asks git-annex to add everything to the annex, but then remove any file contents that it can safely remove. What can it safely remove? Well, anything that it can verify is on another repository such as \"other-disk\"! So, this will happily drop any duplicated file contents, while leaving all the rest alone.
-
-In practice, you might not want to have all your old backup disks mounted at the same time and configured as remotes. Look into configuring [[trust]] to avoid needing do to that. If usb-0 is already a trusted disk, all you need is a simple \"git annex drop\" on usb-1.
-"""]]
diff --git a/doc/bugs/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates/comment_2_4394bde1c6fd44acae649baffe802775._comment b/doc/bugs/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates/comment_2_4394bde1c6fd44acae649baffe802775._comment
deleted file mode 100644
index 04d58a459..000000000
--- a/doc/bugs/wishlist:_Provide_a___34__git_annex__34___command_that_will_skip_duplicates/comment_2_4394bde1c6fd44acae649baffe802775._comment
+++ /dev/null
@@ -1,18 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawkjvjLHW9Omza7x1VEzIFQ8Z5honhRB90I"
- nickname="Asheesh"
- subject="I actually *do* want to avoid duplication of filenames"
- date="2011-01-28T07:30:05Z"
- content="""
-I really do want just one filename per file, at least for some cases.
-
-For my photos, there's no benefit to having a few filenames point to the same file. As I'm putting them all into the git-annex, that is a good time to remove the pure duplicates so that I don't e.g. see them twice when browsing the directory as a gallery. Also, I am uploading my photos to the web, and I want to avoid uploading the same photo (by content) twice.
-
-I hope that makes things clearer!
-
-For now I'm just doing this:
-
-* paulproteus@renaissance:/mnt/backups-terabyte/paulproteus/sd-card-from-2011-01-06/sd-cards/DCIM/100CANON $ for file in *; do hash=$(sha1sum \"$file\"); if ls /home/paulproteus/Photos/in-flickr/.git-annex | grep -q \"$hash\"; then echo already annexed ; else flickr_upload \"$file\" && mv \"$file\" \"/home/paulproteus/Photos/in-flickr/2011-01-28/from-some-nested-sd-card-bk\" && (cd /home/paulproteus/Photos/in-flickr/2011-01-28/from-some-nested-sd-card-bk && git annex add . && git commit -m ...) ; fi; done
-
-(Yeah, Flickr for my photos for now. I feel sad about betraying the principle of autonomo.us-ness.)
-"""]]
diff --git a/doc/bugs/wishlist:___34__git_annex_add__34___multiple_processes.mdwn b/doc/bugs/wishlist:___34__git_annex_add__34___multiple_processes.mdwn
deleted file mode 100644
index f3d383701..000000000
--- a/doc/bugs/wishlist:___34__git_annex_add__34___multiple_processes.mdwn
+++ /dev/null
@@ -1,7 +0,0 @@
-Hello,
-
-i'm in the process of managing my music collection with git-annex. The initial "git annex add" using the sha1 banckend is quite long an i was wondering that it could be nice to launch multiple "sha1sum" processes in parallel to speed up things.
-
-Anyway, thanks for this wonderful piece of software.
-
-Jean-Baptiste
diff --git a/doc/bugs/wishlist:___34__git_annex_add__34___multiple_processes/comment_1_85b14478411a33e6186a64bd41f0910d._comment b/doc/bugs/wishlist:___34__git_annex_add__34___multiple_processes/comment_1_85b14478411a33e6186a64bd41f0910d._comment
deleted file mode 100644
index 2364b7fb8..000000000
--- a/doc/bugs/wishlist:___34__git_annex_add__34___multiple_processes/comment_1_85b14478411a33e6186a64bd41f0910d._comment
+++ /dev/null
@@ -1,10 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 1"
- date="2011-02-25T19:12:42Z"
- content="""
-I'd expect the checksumming to be disk bound, not CPU bound, on most systems.
-
-I suggest you start off on the WORM backend, and then you can run a job later to [[migrate|walkthrough#index14h2]] to the SHA1 backend.
-"""]]
diff --git a/doc/bugs/wishlist:___34__git_annex_add__34___multiple_processes/comment_2_82e857f463cfdf73c70f6c0a9f9a31d6._comment b/doc/bugs/wishlist:___34__git_annex_add__34___multiple_processes/comment_2_82e857f463cfdf73c70f6c0a9f9a31d6._comment
deleted file mode 100644
index 9b8240658..000000000
--- a/doc/bugs/wishlist:___34__git_annex_add__34___multiple_processes/comment_2_82e857f463cfdf73c70f6c0a9f9a31d6._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="http://joey.kitenet.net/"
- nickname="joey"
- subject="comment 2"
- date="2011-02-25T19:54:28Z"
- content="""
-But, see [[todo/parallel_possibilities]]
-"""]]
diff --git a/doc/bugs/wishlist:___34__git_annex_add__34___multiple_processes/comment_3_8af85eba7472d9025c6fae4f03e3ad75._comment b/doc/bugs/wishlist:___34__git_annex_add__34___multiple_processes/comment_3_8af85eba7472d9025c6fae4f03e3ad75._comment
deleted file mode 100644
index ee769f0dd..000000000
--- a/doc/bugs/wishlist:___34__git_annex_add__34___multiple_processes/comment_3_8af85eba7472d9025c6fae4f03e3ad75._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="jbd"
- ip="89.158.228.148"
- subject="comment 3"
- date="2011-02-26T10:26:12Z"
- content="""
-Thank your for your answer and the link !
-"""]]
diff --git a/doc/bugs/wishlist:_support_for_more_ssh_urls_.mdwn b/doc/bugs/wishlist:_support_for_more_ssh_urls_.mdwn
deleted file mode 100644
index 55b8120a7..000000000
--- a/doc/bugs/wishlist:_support_for_more_ssh_urls_.mdwn
+++ /dev/null
@@ -1,22 +0,0 @@
-git-annex does not seem to support all kinds of urls that git does.
-
-Specifically, if I have ~/bar set up on host foo:
-
-    [remote "foo"]
-    ## this one is not recognized as ssh url at all
-    #	url = foo:bar
-    ## this one makes git-annex try to access '/~/bar' literally
-    #	url = ssh://foo/~/bar
-    ## this one works
-    	url = ssh://foo/home/tv/bar
-
-> scp-style is now supported.
-
-> `~` expansions (for the user's home, or other users)
-> are somewhat tricky to support as they require running
-> code on the remote to lookup homedirs. If git-annex grows a
-> `git annex shell` that is run on the remote side
-> (something I am [[considering|todo/git-annex-shell]] for other reasons), it
-> could handle the expansions there. --[[Joey]]
-
-> Update: Now `~` expansions are supported. [[done]]