diff options
Diffstat (limited to 'doc/todo/wishlist__58___use_hardlinks_for_local_clones')
6 files changed, 0 insertions, 83 deletions
diff --git a/doc/todo/wishlist__58___use_hardlinks_for_local_clones/comment_1_85064fafe472a5bd395d60ce8f7acb56._comment b/doc/todo/wishlist__58___use_hardlinks_for_local_clones/comment_1_85064fafe472a5bd395d60ce8f7acb56._comment deleted file mode 100644 index 4ef5f8414..000000000 --- a/doc/todo/wishlist__58___use_hardlinks_for_local_clones/comment_1_85064fafe472a5bd395d60ce8f7acb56._comment +++ /dev/null @@ -1,12 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="4.152.108.220" - subject="comment 1" - date="2013-09-25T17:14:28Z" - content=""" -git-annex uses cp --reflink=auto. So on a filesystem supporting COW file copies, like btrfs, `git annex get` will not use any disk space when getting from the same filesystem. - -I do not like the idea of using hardlinks, because changing the file in one repository would change it in the other, which may not be desired. - -[[union_mounting]] seems to cover this item pretty well, so I will close this as a duplicate. -"""]] diff --git a/doc/todo/wishlist__58___use_hardlinks_for_local_clones/comment_2_ad51dced0c0146e1867830b93b520118._comment b/doc/todo/wishlist__58___use_hardlinks_for_local_clones/comment_2_ad51dced0c0146e1867830b93b520118._comment deleted file mode 100644 index 8476b4220..000000000 --- a/doc/todo/wishlist__58___use_hardlinks_for_local_clones/comment_2_ad51dced0c0146e1867830b93b520118._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawlUGPPMvAP5Hu0NyNqeRMPC4pANeJNHZ0o" - nickname="Sylvain" - subject="why worry about modifications ?" - date="2014-11-02T17:46:57Z" - content=""" -I don't understand why you worry about having one remote modify the file locally which would get propagated to the other because of the hardlinks. When using checksumming, the repos would be pretty screwed if someone would do that anyways. - -In other words, hardlinking the SHA-checksummed files in .git/annex/objects/ across repos and/or between e.g. a directory remote and a repo would sound a pretty safe and nice optimization to me. I am like the OP, deduplication that does not require brtfs would be a great git annex feature. -"""]] diff --git a/doc/todo/wishlist__58___use_hardlinks_for_local_clones/comment_3_650ded07dfb4c0c598f6ae649e45760b._comment b/doc/todo/wishlist__58___use_hardlinks_for_local_clones/comment_3_650ded07dfb4c0c598f6ae649e45760b._comment deleted file mode 100644 index c2e5fa207..000000000 --- a/doc/todo/wishlist__58___use_hardlinks_for_local_clones/comment_3_650ded07dfb4c0c598f6ae649e45760b._comment +++ /dev/null @@ -1,30 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawkHTRzRZoBFEDl9XcTfVveW8yO7CTKMg-o" - nickname="Felix" - subject="use your own cp" - date="2015-02-04T14:16:14Z" - content=""" -As a workaround one could use another cp. Maybe something like this: - -Make an executable shell script \"cp\": - - #!/bin/sh - - p1=\"$1\" - shift - - if [ \"$p1\" = '--reflink=auto' ] ; then - p1='--link' - fi - - exec /bin/cp \"$p1\" \"$@\" - - -And put it into a directory which is found before the \"real\" cp: - - export PATH=/path/to/special/cp/:$PATH - - -This \"cp\" makes a hardlink if the '--reflink=auto' parameter is used (1st). - -"""]] diff --git a/doc/todo/wishlist__58___use_hardlinks_for_local_clones/comment_4_e0be9631d7f017dbff5baaabbd0e2d5c._comment b/doc/todo/wishlist__58___use_hardlinks_for_local_clones/comment_4_e0be9631d7f017dbff5baaabbd0e2d5c._comment deleted file mode 100644 index 69dc0a6ce..000000000 --- a/doc/todo/wishlist__58___use_hardlinks_for_local_clones/comment_4_e0be9631d7f017dbff5baaabbd0e2d5c._comment +++ /dev/null @@ -1,14 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 4""" - date="2015-02-04T20:03:19Z" - content=""" -No, please don't wrap your `cp`. Forcing git-annex to hard link -files like that can result in data loss, in a number of different -scenarios. And it's generally asking for a broken system. - -Since version 5.20140915, you can "git clone --shared" and -this will set up a clone of a repository in which git-annex will -use hardlinks, in a safe and reliable way. (Notably it marks the clone -as untrusted.) -"""]] diff --git a/doc/todo/wishlist__58___use_hardlinks_for_local_clones/comment_5_90aacf46abdeab34ec8e402613da679d._comment b/doc/todo/wishlist__58___use_hardlinks_for_local_clones/comment_5_90aacf46abdeab34ec8e402613da679d._comment deleted file mode 100644 index 0aa945f6b..000000000 --- a/doc/todo/wishlist__58___use_hardlinks_for_local_clones/comment_5_90aacf46abdeab34ec8e402613da679d._comment +++ /dev/null @@ -1,9 +0,0 @@ -[[!comment format=mdwn - username="lealanko" - subject="comment 5" - date="2015-09-06T13:26:49Z" - content=""" -> you can \"git clone --shared\" and this will set up a clone of a repository in which git-annex will use hardlinks - -Copying files from the shared origin repository to the clone will create a hardlink, yes. But copying a file from the clone to the origin will still create a physical copy, even though the situation is quite comparable. Could hardlink support be added in this direction as well? -"""]] diff --git a/doc/todo/wishlist__58___use_hardlinks_for_local_clones/comment_6_3971f77ef70c81e4bf94cd0cab1335ac._comment b/doc/todo/wishlist__58___use_hardlinks_for_local_clones/comment_6_3971f77ef70c81e4bf94cd0cab1335ac._comment deleted file mode 100644 index 68794ce0d..000000000 --- a/doc/todo/wishlist__58___use_hardlinks_for_local_clones/comment_6_3971f77ef70c81e4bf94cd0cab1335ac._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 6""" - date="2015-09-09T18:41:02Z" - content=""" -@lealanko, that's a good point, but a old closed todo item is not the best -place to make such a request. I've opened a new todo item about that. -"""]] |