Error:non-monotonic index after failed recursive sed command

2013-01-14 Thread George Karpenkov
Hi All, I've managed to corrupt my very valuable repository with a recursive sed which went wrong. I wanted to convert all tabs to spaces with the following command: find ./ -name '*.*' -exec sed -i 's/\t//g' {} \; I think that has changed not only the files in the repo, but the data files

Re: Error:non-monotonic index after failed recursive sed command

2013-01-14 Thread Matthieu Moy
George Karpenkov geo...@metaworld.ru writes: Hi All, I've managed to corrupt my very valuable repository with a recursive sed which went wrong. I wanted to convert all tabs to spaces with the following command: find ./ -name '*.*' -exec sed -i 's/\t//g' {} \; Clearly, this is a

Re: Error:non-monotonic index after failed recursive sed command

2013-01-14 Thread John Keeping
On Mon, Jan 14, 2013 at 01:06:16PM +0100, Matthieu Moy wrote: George Karpenkov geo...@metaworld.ru writes: I've managed to corrupt my very valuable repository with a recursive sed which went wrong. I wanted to convert all tabs to spaces with the following command: find ./ -name '*.*' -exec

Re: Error:non-monotonic index after failed recursive sed command

2013-01-14 Thread Johannes Sixt
Am 1/14/2013 12:40, schrieb George Karpenkov: I've managed to corrupt my very valuable repository with a recursive sed which went wrong. I wanted to convert all tabs to spaces with the following command: find ./ -name '*.*' -exec sed -i 's/\t//g' {} \; I think that has changed not

Re: Error:non-monotonic index after failed recursive sed command

2013-01-14 Thread Junio C Hamano
Johannes Sixt j.s...@viscovery.net writes: Am 1/14/2013 12:40, schrieb George Karpenkov: I've managed to corrupt my very valuable repository with a recursive sed which went wrong. I wanted to convert all tabs to spaces with the following command: find ./ -name '*.*' -exec sed -i 's/\t/

Re: Error:non-monotonic index after failed recursive sed command

2013-01-14 Thread Matthieu Moy
Junio C Hamano gits...@pobox.com writes: Everybody seems to be getting an impression that .idx is the only thing that got corrupt. Where does that come from? It's the only thing that appear in the error message. This does not imply that it is the only corrupt thing, but gives a little hope

Re: Error:non-monotonic index after failed recursive sed command

2013-01-14 Thread George Karpenkov
Thanks everyone! Progress so far: After executing reverse sed command: find .git -name '*.*' -exec sed -i 's//\t/g' {} \; And trying to switch the branch I get: git checkout X error: failed to read object 51a980792f26875d00acb79a19f043420f542cfa at offset 41433013 from

Re: Error:non-monotonic index after failed recursive sed command

2013-01-14 Thread Philip Oakley
From: George Karpenkov geo...@metaworld.ru Sent: Monday, January 14, 2013 10:57 PM Thanks everyone! Progress so far: After executing reverse sed command: find .git -name '*.*' -exec sed -i 's//\t/g' {} \; Have you counted how many substitutions there are in the pack file(s). It may be

Re: Error:non-monotonic index after failed recursive sed command

2013-01-14 Thread George Karpenkov
Happy ending! Turns out i have actually made a backup 3 days ago. My other work was on a branch + in a stash. Commits done on a branch were already present in a backup. I was able to get the stash working by copying corrupted .pack files from the backup, luckily all the new work wasn't packed