{"thread":{"id":"178","subject":"Git hangs while executing commit-tree","startedAt":"2005-04-20T21:28:35Z","lastAt":"2005-04-20T22:08:16Z","messageCount":4,"participants":["Rhys Hardwick","Petr Baudis","Linus Torvalds","David Greaves"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"1031","messageId":"200504202228.35652.rhys@rhyshardwick.co.uk","threadId":"178","inReplyTo":null,"subject":"Git hangs while executing commit-tree","fromName":"Rhys Hardwick","fromEmail":"rhys@rhyshardwick.co.uk","sentAt":"2005-04-20T21:28:35Z","receivedAt":"2005-04-20T21:28:35Z","isPatch":false,"sender":{"key":"rhys@rhyshardwick.co.uk","avatar":null},"body":"Hey,\n\nThe following is a copy of the terminal session in question:\n\nrhys@metatron:~/repo/tmp.repo$ ls\nrhys@metatron:~/repo/tmp.repo$ init-db\ndefaulting to local storage area\nrhys@metatron:~/repo/tmp.repo$ ls -l .git\ntotal 4\ndrwxr-xr-x  258 rhys rhys 4096 2005-04-20 20:52 objects\nrhys@metatron:~/repo/tmp.repo$ ls .git/objects/\n00  0d  1a  27  34  41  4e  5b  68  75  82  8f  9c  a9  b6  c3  d0  dd  ea  f7\n01  0e  1b  28  35  42  4f  5c  69  76  83  90  9d  aa  b7  c4  d1  de  eb  f8\n02  0f  1c  29  36  43  50  5d  6a  77  84  91  9e  ab  b8  c5  d2  df  ec  f9\n03  10  1d  2a  37  44  51  5e  6b  78  85  92  9f  ac  b9  c6  d3  e0  ed  fa\n04  11  1e  2b  38  45  52  5f  6c  79  86  93  a0  ad  ba  c7  d4  e1  ee  fb\n05  12  1f  2c  39  46  53  60  6d  7a  87  94  a1  ae  bb  c8  d5  e2  ef  fc\n06  13  20  2d  3a  47  54  61  6e  7b  88  95  a2  af  bc  c9  d6  e3  f0  fd\n07  14  21  2e  3b  48  55  62  6f  7c  89  96  a3  b0  bd  ca  d7  e4  f1  fe\n08  15  22  2f  3c  49  56  63  70  7d  8a  97  a4  b1  be  cb  d8  e5  f2  ff\n09  16  23  30  3d  4a  57  64  71  7e  8b  98  a5  b2  bf  cc  d9  e6  f3\n0a  17  24  31  3e  4b  58  65  72  7f  8c  99  a6  b3  c0  cd  da  e7  f4\n0b  18  25  32  3f  4c  59  66  73  80  8d  9a  a7  b4  c1  ce  db  e8  f5\n0c  19  26  33  40  4d  5a  67  74  81  8e  9b  a8  b5  c2  cf  dc  e9  f6\nrhys@metatron:~/repo/tmp.repo$ find . -type f\nrhys@metatron:~/repo/tmp.repo$ mkdir src\nrhys@metatron:~/repo/tmp.repo$ pico src/hello.c\nrhys@metatron:~/repo/tmp.repo$ pico Makefile\nrhys@metatron:~/repo/tmp.repo$ update-cache -add Makefile src/hello.c\nfatal: unknown option -add\nrhys@metatron:~/repo/tmp.repo$ update-cache --add Makefile src/hello.c\nrhys@metatron:~/repo/tmp.repo$ write-tree\nc80156fafbac377ab35beb076090c8320f874f91\nrhys@metatron:~/repo/tmp.repo$ commit-tree \nc80156fafbac377ab35beb076090c8320f874f91\nCommitting initial tree c80156fafbac377ab35beb076090c8320f874f91\n \n\n\nAt this point, the command seems to be just waiting.  I have had it waiting \nfor around 2 hours now!  I have tried removing ~/repo/tmp.repo and starting \nover, with exactly the same results.\n\nI was testing git by following the tutorial posted by Tony Luck on this list.  \nI updated and built the latest version of git, using git, at around 2000 GMT \ntoday.  I have attached the Makefile and hello.c if anyone finds them useful.\n\nThanks for any help,\n\nRhys\n\n\nhello: src/hello.c\n\tcc -o hello -O src/hello.c\n\n\n\n#include <stdio.h>\n\nmain()\n{\n\tprintf(\"Hello, world!\\n\");\n}\n"},{"id":"1033","messageId":"20050420213513.GG19112@pasky.ji.cz","threadId":"178","inReplyTo":"200504202228.35652.rhys@rhyshardwick.co.uk","subject":"Re: Git hangs while executing commit-tree","fromName":"Petr Baudis","fromEmail":"pasky@ucw.cz","sentAt":"2005-04-20T21:35:14Z","receivedAt":"2005-04-20T21:35:14Z","isPatch":false,"sender":{"key":"pasky@ucw.cz","avatar":"https://avatars.githubusercontent.com/u/18439?v=4"},"body":"Dear diary, on Wed, Apr 20, 2005 at 11:28:35PM CEST, I got a letter\nwhere Rhys Hardwick <rhys@rhyshardwick.co.uk> told me that...\n> Hey,\n\nHi,\n\n> rhys@metatron:~/repo/tmp.repo$ commit-tree \n> c80156fafbac377ab35beb076090c8320f874f91\n> Committing initial tree c80156fafbac377ab35beb076090c8320f874f91\n>  \n> \n> \n> At this point, the command seems to be just waiting.  I have had it waiting \n> for around 2 hours now!  I have tried removing ~/repo/tmp.repo and starting \n> over, with exactly the same results.\n\njust type in your commit message and press ctrl-D now. ;-)\n\nIf you can't get along by peeking at the source when you get stuck, etc,\nyou might prefer using git-pasky (http://pasky.or.cz/~pasky/dev/git/),\nwhich will guide you nicely.\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"},{"id":"1035","messageId":"Pine.LNX.4.58.0504201446510.6467@ppc970.osdl.org","threadId":"178","inReplyTo":"200504202228.35652.rhys@rhyshardwick.co.uk","subject":"Re: Git hangs while executing commit-tree","fromName":"Linus Torvalds","fromEmail":"torvalds@osdl.org","sentAt":"2005-04-20T21:48:17Z","receivedAt":"2005-04-20T21:48:17Z","isPatch":false,"sender":{"key":"torvalds@linux-foundation.org","avatar":"https://avatars.githubusercontent.com/u/1024025?v=4"},"body":"\n\nOn Wed, 20 Apr 2005, Rhys Hardwick wrote:\n>\n> rhys@metatron:~/repo/tmp.repo$ commit-tree  c80156fafbac377ab35beb076090c8320f874f91\n> Committing initial tree c80156fafbac377ab35beb076090c8320f874f91\n>  \n> At this point, the command seems to be just waiting.\n\nThat's _exactly_ what it's doing. It's waiting for you to write a commit \nmessage.\n\nSomething like\n\n\tThis is my initial commit of Hello World!\n\t^D\n\nwill make it happy.\n\nAlternatively, you can certainly just write your message beforehand with \nan editor and just pipe it into commit-tree.\n\n\t\t\tLinus\n"},{"id":"1043","messageId":"4266D2D0.5000503@dgreaves.com","threadId":"178","inReplyTo":"Pine.LNX.4.58.0504201446510.6467@ppc970.osdl.org","subject":"Re: Git hangs while executing commit-tree","fromName":"David Greaves","fromEmail":"david@dgreaves.com","sentAt":"2005-04-20T22:08:16Z","receivedAt":"2005-04-20T22:08:16Z","isPatch":false,"sender":{"key":"david@dgreaves.com","avatar":"https://gravatar.com/avatar/ca67bad50999edcdd137c9a65da2381557d175bea99ae956afdabc5785e42b79?d=mp&s=160"},"body":"Linus Torvalds wrote:\n> \n> On Wed, 20 Apr 2005, Rhys Hardwick wrote:\n> \n>>rhys@metatron:~/repo/tmp.repo$ commit-tree  c80156fafbac377ab35beb076090c8320f874f91\n>>Committing initial tree c80156fafbac377ab35beb076090c8320f874f91\n>> \n>>At this point, the command seems to be just waiting.\n> \n> \n> That's _exactly_ what it's doing. It's waiting for you to write a commit \n> message.\n> \n> Something like\n> \n> \tThis is my initial commit of Hello World!\n> \t^D\n> \n> will make it happy.\n> \n> Alternatively, you can certainly just write your message beforehand with \n> an editor and just pipe it into commit-tree.\n> \n> \t\t\tLinus\n\nWhen someone commits the docs I'll submit the next patch for the README:\n\ncommit-tree\n\tcommit-tree <sha1> [-p <parent sha1>...] < changelog\n\nCreates a new commit object based on the provided tree object and\nemits the new commit object id on stdout. If no parent is given then\nit is considered to be an initial tree.\n\nA commit comment is read from stdin (max 999 chars)\n\nA commit object usually has 1 parent (a commit after a change) or 2\nparents (a merge) although there is no reason it cannot have more than\n2 parents.\n\nWhile a tree represents a particular directory state of a working\ndirectory, a commit represents that state in \"time\", and explains how\nto get there.\n\nNormally a commit would identify a new \"HEAD\" state, and while git\ndoesn't care where you save the note about that state, in practice we\ntend to just write the result to the file \".git/HEAD\", so that we can\nalways see what the last committed state was.\n\nOptions\n\n<sha1>\n\tAn existing tree object\n\n-p <parent sha1>\n\tEach -p indicates a the id of a parent commit object.\n\t\n\nCommit Information\n\nA commit encapsulates:\n\tall parent object ids\n\tauthor name, email and date\n\tcommitter name and email and the commit time.\n\nIf not provided, commit-tree uses your name, hostname and domain to\nprovide author and committer info. This can be overridden using the\nfollowing environment variables.\n\tAUTHOR_NAME\n\tAUTHOR_EMAIL\n\tAUTHOR_DATE\n\tCOMMIT_AUTHOR_NAME\n\tCOMMIT_AUTHOR_EMAIL\n(nb <,> and CRs are stripped)\n\nsee also: write-tree\n\nDavid\n-- \n"}]}