{"thread":{"id":"14148","subject":"how to list all files that will be comitted","startedAt":"2008-06-25T15:31:31Z","lastAt":"2008-06-25T16:24:27Z","messageCount":8,"participants":["Rhodes, Kate","Ian Hilt","Reece Dunn","Karl Hasselström","Michael J Gruber"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"81129","messageId":"644094BE-2835-41EF-B1B4-615B8A4BD509@gmail.com","threadId":"14148","inReplyTo":null,"subject":"how to list all files that will be comitted","fromName":"Rhodes, Kate","fromEmail":"masukomi@gmail.com","sentAt":"2008-06-25T15:31:31Z","receivedAt":"2008-06-25T15:31:31Z","isPatch":false,"sender":{"key":"masukomi@gmail.com","avatar":null},"body":"I know ls-files is the tool I need but I haven't been able to figure \nout what combination of options will give me the files that have been \nadded to the index.\n\n-Kate\n"},{"id":"81131","messageId":"alpine.LFD.1.10.0806251154180.5755@sys-0.hiltweb.site","threadId":"14148","inReplyTo":"644094BE-2835-41EF-B1B4-615B8A4BD509@gmail.com","subject":"Re: how to list all files that will be comitted","fromName":"Ian Hilt","fromEmail":"ian.hilt@gmx.com","sentAt":"2008-06-25T15:57:11Z","receivedAt":"2008-06-25T15:57:11Z","isPatch":false,"sender":{"key":"ian.hilt@gmx.com","avatar":null},"body":"On Wed, 25 Jun 2008 at 11:31am -0400, Rhodes, Kate wrote:\n\n> I know ls-files is the tool I need but I haven't been able to figure out what\n> combination of options will give me the files that have been added to the\n> index.\n> \n> -Kate\n\nHave you tried \"git status\" ? It will output something similar to the\nfollowing:\n\n# On branch master\n# Changes to be committed:\n# (use \"git reset HEAD ...\" to unstage)\n#\n#\tmodified: somefile\n#\n# Changed but not updated:\n# (use \"git add ...\" to update what will be committed)\n#\n#\tmodified: anotherfile\n#\n\n\n-- \nIan Hilt\nIan.Hilt (at) gmx.com\nGnuPG key: 0x4AFC1EE3\n"},{"id":"81132","messageId":"17C0F998-66C0-4DFC-90EB-B85FF6E07844@gmail.com","threadId":"14148","inReplyTo":"alpine.LFD.1.10.0806251154180.5755@sys-0.hiltweb.site","subject":"Re: how to list all files that will be comitted","fromName":"Rhodes, Kate","fromEmail":"masukomi@gmail.com","sentAt":"2008-06-25T16:01:49Z","receivedAt":"2008-06-25T16:01:49Z","isPatch":false,"sender":{"key":"masukomi@gmail.com","avatar":null},"body":"yeah, but i was hoping for plumbing, not porcelain, that showed just \nwhat i wanted so that i didn't have to parse status' output.\n\n-Kate\n\nOn Jun 25, 2008, at 11:57 AM, Ian Hilt wrote:\n\n> Have you tried \"git status\" ? It will output something similar to the\n> following:\n"},{"id":"81135","messageId":"3f4fd2640806250914v7b0ee72aw65f5dfe72790ce3c@mail.gmail.com","threadId":"14148","inReplyTo":"644094BE-2835-41EF-B1B4-615B8A4BD509@gmail.com","subject":"Re: how to list all files that will be comitted","fromName":"Reece Dunn","fromEmail":"msclrhd@googlemail.com","sentAt":"2008-06-25T16:14:39Z","receivedAt":"2008-06-25T16:14:39Z","isPatch":false,"sender":{"key":"msclrhd@googlemail.com","avatar":null},"body":"2008/6/25 Rhodes, Kate :\n> I know ls-files is the tool I need but I haven't been able to figure out\n> what combination of options will give me the files that have been added to\n> the index.\n>\n> -Kate\n\n`git status` will do this, unless you need to do additional processing\non the results.\n\nHTH,\n- Reece\n"},{"id":"81136","messageId":"20080625161439.GA1794@diana.vm.bytemark.co.uk","threadId":"14148","inReplyTo":"17C0F998-66C0-4DFC-90EB-B85FF6E07844@gmail.com","subject":"Re: how to list all files that will be comitted","fromName":"Karl Hasselström","fromEmail":"kha@treskal.com","sentAt":"2008-06-25T16:14:39Z","receivedAt":"2008-06-25T16:14:39Z","isPatch":false,"sender":{"key":"kha@treskal.com","avatar":"https://gravatar.com/avatar/f0120c734b5279b345075a28521e1ac66acb20c9913ffe9bf6ae97e53f7f3f13?d=mp&s=160"},"body":"On 2008-06-25 12:01:49 -0400, Rhodes, Kate wrote:\n\n> yeah, but i was hoping for plumbing, not porcelain, that showed just\n> what i wanted so that i didn't have to parse status' output.\n\nUnless you want a listing of all the files in the index, you probably\nwant to call diff-index.\n\n git diff-index --cached \n\ngives you the diff between the index and a tree-ish. With the\n--name-only option, you get only the filenames and not all the modes,\nblob sha1s, etc.\n\n-- \nKarl Hasselström, kha@treskal.com\n www.treskal.com/kalle\n"},{"id":"81137","messageId":"54450C0E-1AC8-4CE8-919C-8326ACC588EB@gmail.com","threadId":"14148","inReplyTo":"20080625161439.GA1794@diana.vm.bytemark.co.uk","subject":"Re: how to list all files that will be comitted","fromName":"Rhodes, Kate","fromEmail":"masukomi@gmail.com","sentAt":"2008-06-25T16:16:28Z","receivedAt":"2008-06-25T16:16:28Z","isPatch":false,"sender":{"key":"masukomi@gmail.com","avatar":null},"body":"Perfect, exactly what I wanted. Thanks.\n\n-Kate\n\n\nOn Jun 25, 2008, at 12:14 PM, Karl Hasselström wrote:\n\n> On 2008-06-25 12:01:49 -0400, Rhodes, Kate wrote:\n>\n>> yeah, but i was hoping for plumbing, not porcelain, that showed just\n>> what i wanted so that i didn't have to parse status' output.\n>\n> Unless you want a listing of all the files in the index, you probably\n> want to call diff-index.\n>\n> git diff-index --cached \n>\n> gives you the diff between the index and a tree-ish. With the\n> --name-only option, you get only the filenames and not all the modes,\n> blob sha1s, etc.\n>\n> -- \n> Karl Hasselström, kha@treskal.com\n> www.treskal.com/kalle\n"},{"id":"81138","messageId":"g3tr63$fqn$1@ger.gmane.org","threadId":"14148","inReplyTo":"644094BE-2835-41EF-B1B4-615B8A4BD509@gmail.com","subject":"Re: how to list all files that will be comitted","fromName":"Michael J Gruber","fromEmail":"michaeljgruber+gmane@fastmail.fm","sentAt":"2008-06-25T16:19:13Z","receivedAt":"2008-06-25T16:19:13Z","isPatch":false,"sender":{"key":"git@grubix.eu","avatar":"https://avatars.githubusercontent.com/u/233215?v=4"},"body":"Rhodes, Kate venit, vidit, dixit 25.06.2008 17:31:\n> I know ls-files is the tool I need but I haven't been able to figure \n> out what combination of options will give me the files that have been \n> added to the index.\n\nI don't think git ls-files does that, but\n\ngit diff --cached --name-only\n\nwill.\n\nCheers,\nMichael\n"},{"id":"81140","messageId":"alpine.LFD.1.10.0806251219480.5755@sys-0.hiltweb.site","threadId":"14148","inReplyTo":"17C0F998-66C0-4DFC-90EB-B85FF6E07844@gmail.com","subject":"Re: how to list all files that will be comitted","fromName":"Ian Hilt","fromEmail":"ian.hilt@gmx.com","sentAt":"2008-06-25T16:24:27Z","receivedAt":"2008-06-25T16:24:27Z","isPatch":false,"sender":{"key":"ian.hilt@gmx.com","avatar":null},"body":"On Wed, 25 Jun 2008 at 12:01pm -0400, Rhodes, Kate wrote:\n\n> yeah, but i was hoping for plumbing, not porcelain, that showed just what i\n> wanted so that i didn't have to parse status' output.\n\nI wasn't able to make \"git ls-files\" do what you want. However, \"git\ndiff --name-only --cached\" did. It's still porcelain, but it does what\nyou want :)\n\n\n-- \nIan Hilt\nIan.Hilt (at) gmx.com\nGnuPG key: 0x4AFC1EE3\n"}]}