28 Apr '14, 10am

How to fix `rm -f .git/index` #git #useful #dev

fatal: Unable to create '/path/to/repo/.git/index.lock': File exists. If no other git process is currently running, this probably means a git process crashed in this repository earlier. Make sure no other git process is running and remove the file manually to continue. The way to fix this: rm .git/index.lock If you instead do this (note the lack of ".lock" at the end): rm .git/index then your git repo will behave in very weird ways. For instance, git status won't work, and other things break in odd ways. Here's the fix: git read-tree --reset HEAD You'll lose unstaged changes, but you'll have your repo back.

Full article: http://robots.thoughtbot.com/how-to-fix-rm-f-git-index

Tweets

#altann-btctalk - [GOOD] Poll - How should we h...

bitcointalk.org 27 Apr '14, 11pm

PoW is currently stopped at block 10000, leaving only ~400,000 coins in circulation plus 50,450,000 currently being held. ...

っていう記録も残している。

redmine.org 10 May '14, 4am

Added by Toshi MARUYAMA almost 2 years ago scm: git: skip Latin-1 path tests on Git for Windows above 1.7.10 Git for Windo...

Classic Cars Cross the Block at RM Auctions’ Mo...

robbreport.com 28 Apr '14, 7am

Held two weeks in advance of the famed Formula 1 Grand Prix of Monaco , RM Auctions ’ May 10 sale in Monaco brings a diver...

Google Index Status Count Drop After Update Line

Google Index Status Count Drop After Update Line

seroundtable.com 29 Apr '14, 12pm

Google's John Mueller posted an excellent example of a case of where a webmaster is nervous about a report in Google Webma...