Errors received during git pull from linux-2.6.git, but resulting kernel looks OK.

Executive summary: I received some alarming errors while doing
a git pull of the latest kernel from kernel.org, but it appears
that all is well.  Continue reading for the gory details.

I updated my git-pasky tools this morning, by doing "git pasky pull", "make", "make install".

Working from a repo converted yesterday using Linus'instructions and subsequently
successfully updated once:

[steven@spc0 linux-2.6-origin]$ git lsremote
origin  rsync://www.kernel.org/pub/linux/kernel/people/torvalds/linux-2.6.git
[steven@spc0 linux-2.6-origin]$ time git pull origin
MOTD:
MOTD:   Welcome to the Linux Kernel Archive.
MOTD:
MOTD:   Due to U.S. Exports Regulations, all cryptographic software on this
MOTD:   site is subject to the following legal notice:
MOTD:
MOTD:   This site includes publicly available encryption source code
MOTD:   which, together with object code resulting from the compiling of
MOTD:   publicly available source code, may be exported from the United
MOTD:   States under License Exception "TSU" pursuant to 15 C.F.R. Section
MOTD:   740.13(e).
MOTD:
MOTD:   This legal notice applies to cryptographic software only.
MOTD:   Please see the Bureau of Industry and Security,
MOTD:   http://www.bis.doc.gov/ for more information about current
MOTD:   U.S. regulations.
MOTD:


receiving file list ... done
18/13b464853cba4439b3c30412059ed6284114a0
8d/a3a306d0c0c070d87048d14a033df02f40a154
a2/755a80f40e5794ddc20e00f781af9d6320fafb

sent 181 bytes  received 952105 bytes  272081.71 bytes/sec
total size is 63450766  speedup is 66.63

receiving file list ... done
client: nothing to do: perhaps you need to specify some filenames or the --recursive option?
Tree change: 4d78b6c78ae6d87e4c1c8072f42efa716f04afb9:a2755a80f40e5794ddc20e00f781af9d6320fafb
*100644->100644 blob    8e5f9bbdf4de94a1bc4b4da8cb06677ce0a57716->8da3a306d0c0c070d87048d14a033df02f40a154     Makefile
Tracked branch, applying changes...
Fast-forwarding 4d78b6c78ae6d87e4c1c8072f42efa716f04afb9 -> a2755a80f40e5794ddc20e00f781af9d6320fafb
         on top of 4d78b6c78ae6d87e4c1c8072f42efa716f04afb9...
error: bad index version
error: verify header failed
read_cache: Invalid argument
gitdiff.sh: no files matched
error: bad index version
error: verify header failed


real    6m4.771s
user    0m16.538s
sys     0m12.952s
[steven@spc0 linux-2.6-origin]$

Maybe those errors are "harmless".  Checking out the new repo:

[steven@spc0 linux-2.6-origin]$ git export ../linux-2.6.12-rc3
[steven@spc0 linux-2.6-origin]$ cd ..
[steven@spc0 GIT]$ diff -urN linux-2.6.11 linux-2.6.12-rc3 >gitdiff-2.6.12-rc3

So, now I have patch-2.6.12-rc3 from kernel.org and gitdiff-2.6.12-rc3 made above.

[steven@spc0 GIT]$ diffstat gitdiff-2.6.12-rc3 | tail -n 2
  sound/usb/usx2y/usbusx2yaudio.c                              |    1
  4622 files changed, 271839 insertions(+), 156792 deletions(-)

[steven@spc0 GIT]$ diffstat patch-2.6.12-rc3 | tail -n 2
  sound/usb/usx2y/usbusx2yaudio.c                              |    1
  4622 files changed, 271839 insertions(+), 156792 deletions(-)

Despite the errors from the "git pull", the files look OK.

Steven

Dear diary, on Thu, Apr 21, 2005 at 03:55:26PM CEST, I got a letter
where Steven Cole [off-list ref] told me that...

Executive summary: I received some alarming errors while doing
a git pull of the latest kernel from kernel.org, but it appears
that all is well.  Continue reading for the gory details.

It seems that the directory cache format changed since you pulled the
last time.

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor