{"thread":{"id":"43538","subject":"Re: Documentation/git-commit.txt","startedAt":"2006-12-10T00:11:56Z","lastAt":"2006-12-11T14:58:08Z","messageCount":3,"participants":["Andreas Ericsson","Horst H. von Brand","Alan Chandler"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"295387","messageId":"200612100011.kBA0BuTo028252@laptop13.inf.utfsm.cl","threadId":"43538","inReplyTo":"alan@chandlerfamily.org.uk","subject":"Re: Documentation/git-commit.txt","fromName":"Horst H. von Brand","fromEmail":"vonbrand@inf.utfsm.cl","sentAt":"2006-12-10T00:11:56Z","receivedAt":"2006-12-10T00:11:56Z","isPatch":false,"sender":{"key":"vonbrand@inf.utfsm.cl","avatar":"https://avatars.githubusercontent.com/u/211384?v=4"},"body":"Alan Chandler <alan@chandlerfamily.org.uk> wrote:\n\n[...]\n\n> How about the following wording here\n> \n> Instead of staging the content of each file immediately after changing \n> it, you can wait until you have completed all the changes you want to \n> make and then use the `-a` option to tell `git commit` to look for all \n> changes to the content it is tracking and commit it automatically. That \n                 ^^^^^^^\n                 files\n                 (or \"files whose contents\")\n\n> is, this example ...\n\n[Yes, git tracks the contents of files, but it also has a list of files\n whose contents it is tracking]\n-- \nDr. Horst H. von Brand                   User #22616 counter.li.org\nDepartamento de Informatica                    Fono: +56 32 2654431\nUniversidad Tecnica Federico Santa Maria             +56 32 2654239\n"},{"id":"298260","messageId":"200612100923.56707.alan@chandlerfamily.org.uk","threadId":"43538","inReplyTo":"200612100011.kBA0BuTo028252@laptop13.inf.utfsm.cl","subject":"Re: Documentation/git-commit.txt","fromName":"Alan Chandler","fromEmail":"alan@chandlerfamily.org.uk","sentAt":"2006-12-10T09:23:56Z","receivedAt":"2006-12-10T09:23:56Z","isPatch":false,"sender":{"key":"alan@chandlerfamily.org.uk","avatar":"https://gravatar.com/avatar/1862247e5ea8eac114c842f9dc3a5db6253754e24ef7171757cf97eedce48b8c?d=mp&s=160"},"body":"On Sunday 10 December 2006 00:11, Horst H. von Brand wrote:\n> Alan Chandler <alan@chandlerfamily.org.uk> wrote:\n>\n> [...]\n>\n> > How about the following wording here\n> >\n> > Instead of staging the content of each file immediately after\n> > changing it, you can wait until you have completed all the changes\n> > you want to make and then use the `-a` option to tell `git commit`\n> > to look for all changes to the content it is tracking and commit it\n> > automatically. That\n>\n>                  ^^^^^^^\n>                  files\n>                  (or \"files whose contents\")\n>\n> > is, this example ...\n>\n> [Yes, git tracks the contents of files, but it also has a list of\n> files whose contents it is tracking]\n\nregardless, I think \"it\" should become \"them\"\n\n... it is tracking and commit them automatically. \n\n\n\n-- \nAlan Chandler\n"},{"id":"295359","messageId":"457D7200.6010102@op5.se","threadId":"43538","inReplyTo":"200612100923.56707.alan@chandlerfamily.org.uk","subject":"Re: Documentation/git-commit.txt","fromName":"Andreas Ericsson","fromEmail":"ae@op5.se","sentAt":"2006-12-11T14:58:08Z","receivedAt":"2006-12-11T14:58:08Z","isPatch":false,"sender":{"key":"ae@op5.se","avatar":"https://gravatar.com/avatar/426e89595c75a8f5252dd0c989e5fabe5bcac616e68557427ad9aef6b0ca342a?d=mp&s=160"},"body":"Alan Chandler wrote:\n> On Sunday 10 December 2006 00:11, Horst H. von Brand wrote:\n>> Alan Chandler <alan@chandlerfamily.org.uk> wrote:\n>>\n>> [...]\n>>\n>>> How about the following wording here\n>>>\n>>> Instead of staging the content of each file immediately after\n>>> changing it, you can wait until you have completed all the changes\n>>> you want to make and then use the `-a` option to tell `git commit`\n>>> to look for all changes to the content it is tracking and commit it\n>>> automatically. That\n>>                  ^^^^^^^\n>>                  files\n>>                  (or \"files whose contents\")\n>>\n>>> is, this example ...\n>> [Yes, git tracks the contents of files, but it also has a list of\n>> files whose contents it is tracking]\n> \n> regardless, I think \"it\" should become \"them\"\n> \n> ... it is tracking and commit them automatically. \n> \n\nWorks wonderfully, as the syntactically anal will notice that \"them\" \nrefers to \"the changes\" while newbies glossing over the docs will think \nof \"them\" as \"the files\" (which is technically incorrect but amounts to \nthe same thing from that same newbies perspective).\n\n-- \nAndreas Ericsson                   andreas.ericsson@op5.se\nOP5 AB                             www.op5.se\n"}]}