On Thursday 04 September 2008 02:16:24 Tarmigan wrote:ck That doesn't seem to fix "git log path/to/file" cases. The really interesti= ng=20 part is that if I try git log --follow -M -C path/to/file, I don't get any= =20 history at all. (--follow is the culprit, if I remove that I at least get t= he=20 merge commit) git blame still works, and git log --sparse path/to/file works, of=20 course. --sparse makes giving a path a bit pointless, of course, but we=20 probably can live with that for time being. I'm still open for suggestions,= =20 of course. :) Cheers, Kai =2D-=20 Kai Blin WorldForge developer http://www.worldforge.org/ Wine developer http://wiki.winehq.org/KaiBlin Samba team member http://www.samba.org/samba/team/ =2D- Will code for cotton.
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Bart Van Assche | Integration of SCST in the mainstream Linux kernel |
| Jeff Garzik | Re: fallocate-implementation-on-i86-x86_64-and-powerpc.patch |
git: | |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Arjan van de Ven | Re: [GIT]: Networking |
| Gerrit Renker | [PATCH 15/37] dccp: Set per-connection CCIDs via socket options |
| Natalie Protasevich | [BUG] New Kernel Bugs |
