Geek asks and answers

How to delete large files from Mercurial repo

See also this question .

Not knowing what I was doing, I turned on the large file extension, transferred the file and pressed it into the oven. Now I know the error of my ways, and I need to return this change forever.

I followed SO directions on this; and I can delete large files locally, but this does not affect the remote repositories in the oven. I tried to open the repo in KilnRepositories on the Kiln server and nuking the folder of large files (and also delete the "large files" from the file of the required files), but after a few taps / pulls out the folder, and the query string is returned.

Is there any way to make this permanent? (The setup requires readonly to not work either).

+5
source share
1 answer

Note. This is true, at least for (for Windows) TortoiseHg 2.4 (Mercurial 2.2.1) → 2.7.1 (Mercurial 2.5.2). I will not speak for future or older versions.

After looking at the various available mercury extensions, I came to the conclusion that, as a rule, it is not possible to convert the repository “backward” after the file has been committed using the large file extension.

Firstly, there are two arguments in favor of why you do not want large files to play in your repositories: one and two .

, , ".hglf" . A backout , , ".hglf". mercurial , " " /.hg/requires, . hg .

1: ( , ), , mq extension strip . , , , .

2: phase ( ), ( ), mq hg qpop. , , . , , , / . , , mq .

3: ( ), // ( , ), hg rebase, . , mq. , mq .

4. , transplant graft, (, ), hg , mq strip , .

5: ( ). , : clone_to_keep, clone_to_destroy. clone_to_keep . Mq . , . clone_to_destroy . Windows /clone _to_destroy, .hg .hglf, /clone _to_keep. clone_to_keep . clone_to_destroy readonly .

6: . , ( , CI ..), SO post hg convert. , ; , . , - . , , , .

( , , ).

, , . . - .

+10

More articles:


All Articles