Re: [PATCH v3 4/7] fsl_pq_mdio: Add Suport for etsec2.0 devices.
From: David Miller <davem@davemloft.net>
Date: 2009-10-30 08:44:30
From: David Miller <davem@davemloft.net>
Date: 2009-10-30 08:44:30
From: "Kumar Gopalpet-B05799" <redacted> Date: Fri, 30 Oct 2009 14:12:22 +0530
We were referring to the logs shown on the gitweb. The tree log does not show this commit. (search for this commit id failed) http://git.kernel.org/?p=linux%2Fkernel%2Fgit%2Fdavem%2Fnet-next-2.6.git &a=search&h=29906f6a427d2004a515ebbcdc7b28bae8f6c19c&st=commit&s=e72701a cbe0b35e52d3f04d442837c06b4e64f1c Whereas, the log for the file does show the commit. http://git.kernel.org/?p=linux/kernel/git/davem/net-next-2.6.git;a=histo ry;f=drivers/net/fsl_pq_mdio.c;h=6ac4648669728421b934d32646ffbb626128387 6;hb=HEAD Why is there such a mismatch on the tree itself?
If you are using HTTP for accessing my GIT tree(s) that's your problem. I do not update the web based GIT information when I push into my tree(s), only the GIT and SSH protocols are reliable ways to clone and access my tree(s).