[git-users] Damaged repo
Hello -- Not sure how much harm this could do, but I run git via windows -- I ran a shell script that would lower-case files in the directory and all subdirectories -- I forgot one of those sub-dirs was a git ripo (.git) and all the files in it were lower cased -- Is there a way to repair this repo? Thanks -- You received this message because you are subscribed to the Google Groups Git for human beings group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [git-users] Damaged repo
From: fpefpe fpespos...@gmail.com Hello -- Not sure how much harm this could do, but I run git via windows -- I ran a shell script that would lower-case files in the directory and all subdirectories -- I forgot one of those sub-dirs was a git ripo (.git) and all the files in it were lower cased -- Is there a way to repair this repo? Thanks If it just lower-cased the file *names*, you can probably fix that manually by comparing with a known-good repository. If you lower-cased the file *contents*, that's going to be a horrible to fix, because the recorded file contents are now wrong. Dale -- You received this message because you are subscribed to the Google Groups Git for human beings group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [git-users] Damaged repo
Thanks for the info -- as it turned out, the used was dropbox creating conflict files in the directory --- my dir/repo is part of my dropbox tree -- once I removed those files it fsck worked ok - thx On Thu, May 8, 2014 at 3:48 PM, Dale R. Worley wor...@alum.mit.edu wrote: From: fpefpe fpespos...@gmail.com Hello -- Not sure how much harm this could do, but I run git via windows -- I ran a shell script that would lower-case files in the directory and all subdirectories -- I forgot one of those sub-dirs was a git ripo (.git) and all the files in it were lower cased -- Is there a way to repair this repo? Thanks If it just lower-cased the file *names*, you can probably fix that manually by comparing with a known-good repository. If you lower-cased the file *contents*, that's going to be a horrible to fix, because the recorded file contents are now wrong. Dale -- You received this message because you are subscribed to a topic in the Google Groups Git for human beings group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/git-users/HCnObVPckUU/unsubscribe. To unsubscribe from this group and all its topics, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Git for human beings group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
