{"thread":{"id":"201","subject":"Errors received during git pull from linux-2.6.git, but resulting kernel looks OK.","startedAt":"2005-04-21T13:55:26Z","lastAt":"2005-04-21T16:04:30Z","messageCount":2,"participants":["Steven Cole","Petr Baudis"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"1128","messageId":"4267B0CE.7020504@mesatop.com","threadId":"201","inReplyTo":null,"subject":"Errors received during git pull from linux-2.6.git, but resulting kernel looks OK.","fromName":"Steven Cole","fromEmail":"elenstev@mesatop.com","sentAt":"2005-04-21T13:55:26Z","receivedAt":"2005-04-21T13:55:26Z","isPatch":false,"sender":{"key":"elenstev@mesatop.com","avatar":null},"body":"Executive summary: I received some alarming errors while doing\na git pull of the latest kernel from kernel.org, but it appears\nthat all is well.  Continue reading for the gory details.\n\nI updated my git-pasky tools this morning, by doing \"git pasky pull\", \"make\", \"make install\".\n\nWorking from a repo converted yesterday using Linus'instructions and subsequently\nsuccessfully updated once:\n\n[steven@spc0 linux-2.6-origin]$ git lsremote\norigin  rsync://www.kernel.org/pub/linux/kernel/people/torvalds/linux-2.6.git\n[steven@spc0 linux-2.6-origin]$ time git pull origin\nMOTD:\nMOTD:   Welcome to the Linux Kernel Archive.\nMOTD:\nMOTD:   Due to U.S. Exports Regulations, all cryptographic software on this\nMOTD:   site is subject to the following legal notice:\nMOTD:\nMOTD:   This site includes publicly available encryption source code\nMOTD:   which, together with object code resulting from the compiling of\nMOTD:   publicly available source code, may be exported from the United\nMOTD:   States under License Exception \"TSU\" pursuant to 15 C.F.R. Section\nMOTD:   740.13(e).\nMOTD:\nMOTD:   This legal notice applies to cryptographic software only.\nMOTD:   Please see the Bureau of Industry and Security,\nMOTD:   http://www.bis.doc.gov/ for more information about current\nMOTD:   U.S. regulations.\nMOTD:\n\n\nreceiving file list ... done\n18/13b464853cba4439b3c30412059ed6284114a0\n8d/a3a306d0c0c070d87048d14a033df02f40a154\na2/755a80f40e5794ddc20e00f781af9d6320fafb\n\nsent 181 bytes  received 952105 bytes  272081.71 bytes/sec\ntotal size is 63450766  speedup is 66.63\n\nreceiving file list ... done\nclient: nothing to do: perhaps you need to specify some filenames or the --recursive option?\nTree change: 4d78b6c78ae6d87e4c1c8072f42efa716f04afb9:a2755a80f40e5794ddc20e00f781af9d6320fafb\n*100644->100644 blob    8e5f9bbdf4de94a1bc4b4da8cb06677ce0a57716->8da3a306d0c0c070d87048d14a033df02f40a154     Makefile\nTracked branch, applying changes...\nFast-forwarding 4d78b6c78ae6d87e4c1c8072f42efa716f04afb9 -> a2755a80f40e5794ddc20e00f781af9d6320fafb\n         on top of 4d78b6c78ae6d87e4c1c8072f42efa716f04afb9...\nerror: bad index version\nerror: verify header failed\nread_cache: Invalid argument\ngitdiff.sh: no files matched\nerror: bad index version\nerror: verify header failed\n\n\nreal    6m4.771s\nuser    0m16.538s\nsys     0m12.952s\n[steven@spc0 linux-2.6-origin]$\n\nMaybe those errors are \"harmless\".  Checking out the new repo:\n\n[steven@spc0 linux-2.6-origin]$ git export ../linux-2.6.12-rc3\n[steven@spc0 linux-2.6-origin]$ cd ..\n[steven@spc0 GIT]$ diff -urN linux-2.6.11 linux-2.6.12-rc3 >gitdiff-2.6.12-rc3\n\nSo, now I have patch-2.6.12-rc3 from kernel.org and gitdiff-2.6.12-rc3 made above.\n\n[steven@spc0 GIT]$ diffstat gitdiff-2.6.12-rc3 | tail -n 2\n  sound/usb/usx2y/usbusx2yaudio.c                              |    1\n  4622 files changed, 271839 insertions(+), 156792 deletions(-)\n\n[steven@spc0 GIT]$ diffstat patch-2.6.12-rc3 | tail -n 2\n  sound/usb/usx2y/usbusx2yaudio.c                              |    1\n  4622 files changed, 271839 insertions(+), 156792 deletions(-)\n\nDespite the errors from the \"git pull\", the files look OK.\n\nSteven\n"},{"id":"1138","messageId":"20050421160430.GA30991@pasky.ji.cz","threadId":"201","inReplyTo":"4267B0CE.7020504@mesatop.com","subject":"Re: Errors received during git pull from linux-2.6.git, but resulting kernel looks OK.","fromName":"Petr Baudis","fromEmail":"pasky@ucw.cz","sentAt":"2005-04-21T16:04:30Z","receivedAt":"2005-04-21T16:04:30Z","isPatch":false,"sender":{"key":"pasky@ucw.cz","avatar":"https://avatars.githubusercontent.com/u/18439?v=4"},"body":"Dear diary, on Thu, Apr 21, 2005 at 03:55:26PM CEST, I got a letter\nwhere Steven Cole <elenstev@mesatop.com> told me that...\n> Executive summary: I received some alarming errors while doing\n> a git pull of the latest kernel from kernel.org, but it appears\n> that all is well.  Continue reading for the gory details.\n\nIt seems that the directory cache format changed since you pulled the\nlast time.\n\n-- \n\t\t\t\tPetr \"Pasky\" Baudis\nStuff: http://pasky.or.cz/\nC++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor\n"}]}