Comments for Source.kohlerville.com

Comment on untrack files in git by Antônio Carlos

Antônio Carlos — Fri, 03 Feb 2012 13:13:49 +0000

Thanks!!! =D

Comment on nwrecover directed recover failure by none

none — Mon, 28 Nov 2011 18:00:52 +0000

Yeah, I just came across this problem. The supports solution is poor, especially since the recover is 244Gb of data, and there is no where on the backup server to restore it. Clearly, this is not an Enterprise product. I’ll try NFS…

Comment on untrack files in git by Michael Härtl

Michael Härtl — Wed, 09 Nov 2011 14:58:11 +0000

I tried the git update-index. It does nothing for me. When i have local changes in the file, git status doesn't show them. But when i try to switch branches, it will not let me due to local changes in that file, that might be overwritten. Can it be a problem that i added this file to .gitignore?

Comment on untrack files in git by AndrewJohnson

AndrewJohnson — Thu, 08 Sep 2011 21:31:29 +0000

When I do this for a file locally and then push it to a shed repository and someone else pulls it down is the assume-unchanged entry there for them as well?

Comment on Adding identi.ca support on seesmic android app by Mustard Lee

Mustard Lee — Wed, 17 Aug 2011 18:40:25 +0000

Thanks for the How To. It’s the second time I’ve googled this tip and arrived at this page. Both time were a ‘thumbs up’ experience.

Comment on lbcd stuck in stat D state wchan sync_p by Ryan

Ryan — Mon, 25 Jul 2011 03:25:58 +0000

We updated to Centos 5.5 and the problem never happened again. Maybe it was a kernel bug that got fixed?

Comment on lbcd stuck in stat D state wchan sync_p by ahirudin

ahirudin — Mon, 25 Jul 2011 03:07:35 +0000

did you manage to solve your issues?

Comment on untrack files in git by Colin Thomas-Arnold

Colin Thomas-Arnold — Fri, 08 Jul 2011 00:22:19 +0000

I think more emphasis should be placed on using:

git update-index --assume-unchanged [path]

per Jonathan Métillon’s comment. It’s MUCH nicer when you’re working collaboratively. +1!

git rm --cached is “correct” when you want to be the only one who still has the file. Other people have pointed this out, I’m just pointing it out again.

Comment on compile amber 11 cuda on centos linux by Ryan

Ryan — Wed, 22 Jun 2011 19:52:51 +0000

Thanks for the reply and the link. I’ll probably update the post when I get around to recompiling with the new fixes.

Comment on compile amber 11 cuda on centos linux by Maria

Maria — Wed, 22 Jun 2011 17:54:04 +0000

I actually have the latest fixes in both Ambertools and Amber 11… so the problems seem to persist.
Thanks. the article was helpful for me to double check what I was doing.
Looks like some of the failures might be due to gcc 4.1.2 incompatibility with Amber on centos.
http://jebnor.blogspot.com/2010/08/installing-amber-11-on-centos-43.html