{"thread":{"id":"50671","subject":"did we ever resolve what \"known to Git\" should mean?","startedAt":"2019-03-06T14:44:50Z","lastAt":"2019-03-06T14:44:50Z","messageCount":1,"participants":["Robert P. J. Day"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"370815","messageId":"alpine.LFD.2.21.1903060940470.6367@localhost.localdomain","threadId":"50671","inReplyTo":null,"subject":"did we ever resolve what \"known to Git\" should mean?","fromName":"Robert P. J. Day","fromEmail":"rpjday@crashcourse.ca","sentAt":"2019-03-06T14:44:44Z","receivedAt":"2019-03-06T14:44:50Z","isPatch":false,"sender":{"key":"rpjday@crashcourse.ca","avatar":"https://avatars.githubusercontent.com/u/226084077?v=4"},"body":"\n  going back to a couple threads:\n\nhttps://marc.info/?l=git&m=151048015116473&w=2\nhttps://marc.info/?l=git&m=152690160605723&w=2\n\nand i'm going to try to clarify what (if anything) was decided\nregarding the internally inconsistent phrase \"known to Git.\" junio's\ntake on this here:\n\nhttps://marc.info/?l=git&m=152695527902711&w=2\n\nwas to banish the phrase entirely in favour of some combination of\n\"tracked\" and/or \"added to the index.\"\n\n  thoughts?\n\nrday\n\n-- \n\n========================================================================\nRobert P. J. Day                                 Ottawa, Ontario, CANADA\n                  http://crashcourse.ca/dokuwiki\n\nTwitter:                                       http://twitter.com/rpjday\nLinkedIn:                               http://ca.linkedin.com/in/rpjday\n========================================================================\n"}]}