{"thread":{"id":"21010","subject":"Documentation problems","startedAt":"2009-09-20T17:58:36Z","lastAt":"2009-09-20T20:52:13Z","messageCount":5,"participants":["Bruce Korb","Matthieu Moy","Andreas Schwab"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"123545","messageId":"4AB66D4C.70301@gmail.com","threadId":"21010","inReplyTo":null,"subject":"Documentation problems","fromName":"Bruce Korb","fromEmail":"bruce.korb@gmail.com","sentAt":"2009-09-20T17:58:36Z","receivedAt":"2009-09-20T17:58:36Z","isPatch":false,"sender":{"key":"bruce.korb@gmail.com","avatar":"https://gravatar.com/avatar/86d91467dc7cc8466a9d133a7b93a5d21233052017c144c9a6f6f7e5110344d0?d=mp&s=160"},"body":"Hi,\n\nI'm trying to figure out what a ``tree-ish''.\nI cannot seem to use many of the commands until I know.\n\n\n Indicates a tree, commit or tag object name. A command that takes a\n argument ultimately wants to operate on a object\n but automatically dereferences and objects that point at a .\n\nI need a translation. :( Thank you. Regards, Bruce\n\nP.S. I have a SuSE installation with everything relating to GIT installed.\nThe man pages reference commands like, \"git-ls-tree --name-only\" except\nthat there isn't any such command. Unless you reverse engineer the\nimplementation of \"git\", discover the /usr/lib/git directory and add it\nto your path. That hassle is rather inconvenient. More hints about\nwhere the git commands get squirreled away would be useful. Thank you.\n"},{"id":"123546","messageId":"vpqvdjdzd6x.fsf@bauges.imag.fr","threadId":"21010","inReplyTo":"4AB66D4C.70301@gmail.com","subject":"Re: Documentation problems","fromName":"Matthieu Moy","fromEmail":"matthieu.moy@grenoble-inp.fr","sentAt":"2009-09-20T18:24:54Z","receivedAt":"2009-09-20T18:24:54Z","isPatch":false,"sender":{"key":"matthieu.moy@grenoble-inp.fr","avatar":"https://gravatar.com/avatar/72c8a2705971a25dfaff23cece15130d405685845d911aedd5667ace277f3fc5?d=mp&s=160"},"body":"Bruce Korb writes:\n\n> Hi,\n>\n> I'm trying to figure out what a ``tree-ish''.\n> I cannot seem to use many of the commands until I know.\n>\n> \n> Indicates a tree, commit or tag object name. A command that takes a\n> argument ultimately wants to operate on a object\n> but automatically dereferences and objects that point at a .\n>\n> I need a translation. :( Thank you. Regards, Bruce\n\ntree = directory (with its content).\n\nFor example, the last commit in the current branch is a Git object of\ntype \"commit\", which contains mostly a log message, a few headers, and\na pointer to the tree object corresponding to the content of the\ndirectory in which you made the commit (modulo what you excluded from\nthe commit of course). Therefore, the name of this commit, although\nnot really a tree, is a tree-ish in that it talks about one and only\none tree. You could name it HEAD, a sha1sum (like\n5a2abc12d64a5e00daa6aebbb673715f365a564a), the name of the branch\n(like \"master\"), ...\n\n> P.S. I have a SuSE installation with everything relating to GIT installed.\n> The man pages reference commands like, \"git-ls-tree --name-only\" except\n> that there isn't any such command. Unless you reverse engineer the\n> implementation of \"git\", discover the /usr/lib/git directory and add it\n> to your path. That hassle is rather inconvenient. More hints about\n> where the git commands get squirreled away would be useful. Thank\n> you.\n\nJust type \"git ls-tree --name-only\". git-ls-tree is the old way to\nrefer to the command name. Normally, any reference to dashed names\nshould have been removed from the documentation by now (so most likely\nyou see it in your distro because it's an old enough version,\notherwise, it's a bug in the doc).\n\n-- \nMatthieu Moy\nhttp://www-verimag.imag.fr/~moy/\n"},{"id":"123547","messageId":"4AB67665.10402@gmail.com","threadId":"21010","inReplyTo":"vpqvdjdzd6x.fsf@bauges.imag.fr","subject":"Re: Documentation problems","fromName":"Bruce Korb","fromEmail":"bruce.korb@gmail.com","sentAt":"2009-09-20T18:37:25Z","receivedAt":"2009-09-20T18:37:25Z","isPatch":false,"sender":{"key":"bruce.korb@gmail.com","avatar":"https://gravatar.com/avatar/86d91467dc7cc8466a9d133a7b93a5d21233052017c144c9a6f6f7e5110344d0?d=mp&s=160"},"body":"Hi Matthieu,\n>> I'm trying to figure out what a ``tree-ish''.\n\n>> I need a translation. :( Thank you. Regards, Bruce\n> \n> tree = directory (with its content).\n> \n> For example, the last commit in the current branch is a Git object of\n> type \"commit\", which contains mostly a log message, a few headers, and\n> a pointer to the tree object corresponding to the content of the\n> directory in which you made the commit (modulo what you excluded from\n> the commit of course). Therefore, the name of this commit, although\n> not really a tree, is a tree-ish in that it talks about one and only\n> one tree. You could name it HEAD, a sha1sum (like\n> 5a2abc12d64a5e00daa6aebbb673715f365a564a), the name of the branch\n> (like \"master\"), ...\n\nSince I haven't created any any branches (to my knowledge), it seems\nthat \"master\" is the magic branch name. My goal was just to get a\nlist of managed files. Is \"master\" going to remain my \"HEAD\" now?\n(Assuming I don't do something to make a new branch. One branch\nis enough for my little one person project....)\n\n> Just type \"git ls-tree --name-only\".\nAh. Thank you.\n> git-ls-tree is the old way to\n> refer to the command name. Normally, any reference to dashed names\n> should have been removed from the documentation by now (so most likely\n> you see it in your distro because it's an old enough version,\n> otherwise, it's a bug in the doc).\n\n$ git --version\ngit version 1.6.0.2\n\nI guess the man pages and installation were out of sync for that release.\n\nThank you for the quick reply! Regards, Bruce\n"},{"id":"123548","messageId":"vpqeiq1zc9f.fsf@bauges.imag.fr","threadId":"21010","inReplyTo":"4AB67665.10402@gmail.com","subject":"Re: Documentation problems","fromName":"Matthieu Moy","fromEmail":"matthieu.moy@grenoble-inp.fr","sentAt":"2009-09-20T18:45:00Z","receivedAt":"2009-09-20T18:45:00Z","isPatch":false,"sender":{"key":"matthieu.moy@grenoble-inp.fr","avatar":"https://gravatar.com/avatar/72c8a2705971a25dfaff23cece15130d405685845d911aedd5667ace277f3fc5?d=mp&s=160"},"body":"Bruce Korb writes:\n\n> Since I haven't created any any branches (to my knowledge), it seems\n> that \"master\" is the magic branch name.\n\nI wouldn't say \"magic\", but surely the default ;-).\n\n> My goal was just to get a list of managed files.\n\nJust cd /where/your/repo/is\ngit ls-files\n\n> Is \"master\" going to remain my \"HEAD\" now?\n\nYes.\n\n>> git-ls-tree is the old way to\n>> refer to the command name. Normally, any reference to dashed names\n>> should have been removed from the documentation by now (so most likely\n>> you see it in your distro because it's an old enough version,\n>> otherwise, it's a bug in the doc).\n>\n> $ git --version\n> git version 1.6.0.2\n>\n> I guess the man pages and installation were out of sync for that release.\n\nWell, actually, a few more instances of dashed commands were removed\nmore recently. That said, to get the doc for \"git foo\", you still have\nto type \"man git-foo\" (or git foo --help indeed), but that's because\n\"man git foo\" means something different to man.\n\n-- \nMatthieu Moy\nhttp://www-verimag.imag.fr/~moy/\n"},{"id":"123554","messageId":"m2zl8p9w5e.fsf@igel.home","threadId":"21010","inReplyTo":"4AB66D4C.70301@gmail.com","subject":"Re: Documentation problems","fromName":"Andreas Schwab","fromEmail":"schwab@linux-m68k.org","sentAt":"2009-09-20T20:52:13Z","receivedAt":"2009-09-20T20:52:13Z","isPatch":false,"sender":{"key":"schwab@linux-m68k.org","avatar":"https://avatars.githubusercontent.com/u/2175493?v=4"},"body":"Bruce Korb writes:\n\n> I'm trying to figure out what a ``tree-ish''.\n> I cannot seem to use many of the commands until I know.\n>\n> \n> Indicates a tree, commit or tag object name. A command that takes a\n> argument ultimately wants to operate on a object\n> but automatically dereferences and objects that point at a .\n>\n> I need a translation. :( Thank you. Regards, Bruce\n\nSee gitglossary(7).\n\nAndreas.\n\n-- \nAndreas Schwab, schwab@linux-m68k.org\nGPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5\n\"And now for something completely different.\"\n"}]}