{"thread":{"id":"40434","subject":"git commit -a -m is not working","startedAt":"2015-09-26T18:51:12Z","lastAt":"2015-09-28T23:34:46Z","messageCount":4,"participants":["Alex Radulescu","brian m. carlson","Jonathan Nieder"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"270784","messageId":"CAMWrOy7YoAofbzfW+dy=v1TRgWGe5OuZ8U2x+Q-XCKc1y_agRA@mail.gmail.com","threadId":"40434","inReplyTo":null,"subject":"git commit -a -m is not working","fromName":"Alex Radulescu","fromEmail":"mydesweb@gmail.com","sentAt":"2015-09-26T18:51:12Z","receivedAt":"2015-09-26T18:51:12Z","isPatch":false,"sender":{"key":"mydesweb@gmail.com","avatar":null},"body":"Hi,\n\nThis command is not working. Any advice?\n\nAlex:testGit Alex$ git commit -a -m 'made a change'\n\nOn branch v1.0\n\nUntracked files:\n\nnew_branch.txt\n\nnothing added to commit but untracked files present\n"},{"id":"270785","messageId":"20150926185416.GA233088@vauxhall.crustytoothpaste.net","threadId":"40434","inReplyTo":"CAMWrOy7YoAofbzfW+dy=v1TRgWGe5OuZ8U2x+Q-XCKc1y_agRA@mail.gmail.com","subject":"Re: git commit -a -m is not working","fromName":"brian m. carlson","fromEmail":"sandals@crustytoothpaste.net","sentAt":"2015-09-26T18:54:16Z","receivedAt":"2015-09-26T18:54:16Z","isPatch":false,"sender":{"key":"sandals@crustytoothpaste.net","avatar":"https://avatars.githubusercontent.com/u/497054?v=4"},"body":"On Sat, Sep 26, 2015 at 09:51:12PM +0300, Alex Radulescu wrote:\n> Hi,\n> \n> This command is not working. Any advice?\n> \n> Alex:testGit Alex$ git commit -a -m 'made a change'\n> \n> On branch v1.0\n> \n> Untracked files:\n> \n> new_branch.txt\n> \n> nothing added to commit but untracked files present\n\ngit commit -a does not add untracked files.  Such files might be build\nby-products or such and you haven't told Git to track them, so it\ndoesn't.\n\nFrom git-commit(1):\n  -a, --all\n      Tell the command to automatically stage files that have been\n      modified and deleted, but new files you have not told Git about\n      are not affected.\n-- \nbrian m. carlson / brian with sandals: Houston, Texas, US\n+1 832 623 2791 | https://www.crustytoothpaste.net/~bmc | My opinion only\nOpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187\n"},{"id":"270818","messageId":"20150928171132.GA11993@google.com","threadId":"40434","inReplyTo":"20150926185416.GA233088@vauxhall.crustytoothpaste.net","subject":"Re: git commit -a -m is not working","fromName":"Jonathan Nieder","fromEmail":"jrnieder@gmail.com","sentAt":"2015-09-28T17:11:32Z","receivedAt":"2015-09-28T17:11:32Z","isPatch":false,"sender":{"key":"jrnieder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/281595?v=4"},"body":"Hi,\n\nbrian m. carlson wrote:\n> On Sat, Sep 26, 2015 at 09:51:12PM +0300, Alex Radulescu wrote:\n\n>> Alex:testGit Alex$ git commit -a -m 'made a change'\n>>\n>> On branch v1.0\n>>\n>> Untracked files:\n>>\n>> new_branch.txt\n>>\n>> nothing added to commit but untracked files present\n>\n> git commit -a does not add untracked files.  Such files might be build\n> by-products or such and you haven't told Git to track them, so it\n> doesn't.\n\nYou can run \"git add -N <files>\" to tell Git to start caring about\nsome new files (e.g., \"git add -N .\" to track them all).\n\nAlternatively, you can run \"git add <files>\" to tell Git that the\ncurrent content of those files is ready for commit (e.g., \"git add .\"\nbefore \"git status\" and \"git commit\" to commit everything).\n\nMore details are at http://jk.gs/gittutorial.html#_making_changes\n(also available by running \"git help tutorial\").\n\nThanks and hope that helps,\nJonathan\n"},{"id":"270900","messageId":"CAMWrOy72tRz3VQ2WGwe6bUD6UyTxLp71TsVeGThRVJgrtQCM+A@mail.gmail.com","threadId":"40434","inReplyTo":"20150928171132.GA11993@google.com","subject":"Re: git commit -a -m is not working","fromName":"Alex Radulescu","fromEmail":"mydesweb@gmail.com","sentAt":"2015-09-28T23:34:46Z","receivedAt":"2015-09-28T23:34:46Z","isPatch":false,"sender":{"key":"mydesweb@gmail.com","avatar":null},"body":"Hi,\n\nThank you for your quick and precise support.\n\nCan you share with me some best practices in deploying a web project?\nI wave one remote repository, many local repositories (each/developer)\nand a shared hosting server. What should I do to push quickly all\nchanges to my shared server?\n\nAlex\n\n2015-09-28 20:11 GMT+03:00 Jonathan Nieder <jrnieder@gmail.com>:\n> Hi,\n>\n> brian m. carlson wrote:\n>> On Sat, Sep 26, 2015 at 09:51:12PM +0300, Alex Radulescu wrote:\n>\n>>> Alex:testGit Alex$ git commit -a -m 'made a change'\n>>>\n>>> On branch v1.0\n>>>\n>>> Untracked files:\n>>>\n>>> new_branch.txt\n>>>\n>>> nothing added to commit but untracked files present\n>>\n>> git commit -a does not add untracked files.  Such files might be build\n>> by-products or such and you haven't told Git to track them, so it\n>> doesn't.\n>\n> You can run \"git add -N <files>\" to tell Git to start caring about\n> some new files (e.g., \"git add -N .\" to track them all).\n>\n> Alternatively, you can run \"git add <files>\" to tell Git that the\n> current content of those files is ready for commit (e.g., \"git add .\"\n> before \"git status\" and \"git commit\" to commit everything).\n>\n> More details are at http://jk.gs/gittutorial.html#_making_changes\n> (also available by running \"git help tutorial\").\n>\n> Thanks and hope that helps,\n> Jonathan\n"}]}