{"thread":{"id":"21623","subject":".gitignore polution","startedAt":"2009-11-14T23:57:31Z","lastAt":"2009-11-16T00:22:41Z","messageCount":3,"participants":["Sverre Rabbelier","Jeff King"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"127573","messageId":"fabb9a1e0911141557k5f6b0b8aud48b95784a9da4e3@mail.gmail.com","threadId":"21623","inReplyTo":null,"subject":".gitignore polution","fromName":"Sverre Rabbelier","fromEmail":"srabbelier@gmail.com","sentAt":"2009-11-14T23:57:31Z","receivedAt":"2009-11-14T23:57:31Z","isPatch":false,"sender":{"key":"srabbelier@gmail.com","avatar":"https://avatars.githubusercontent.com/u/3098?v=4"},"body":"Heya,\n\nI usually compile git from next (sometimes pu to test out a new\nfeature), and when I then switch back to a development branch (usually\nbased off master) I get something like this:\n\n$ git status\n# On branch remote-helpers\n# Untracked files:\n#   (use \"git add <file>...\" to include in what will be committed)\n#\n#\tgit-http-backend\n#\tgit-notes\n#\tgit-remote-hg\n#\ttest-index-version\n\nNow I can easily do 'git clean -f', but it's somewhat annoying. How do\nother developers deal with this?\n\n-- \nCheers,\n\nSverre Rabbelier\n"},{"id":"127597","messageId":"20091115094352.GA21477@coredump.intra.peff.net","threadId":"21623","inReplyTo":"fabb9a1e0911141557k5f6b0b8aud48b95784a9da4e3@mail.gmail.com","subject":"Re: .gitignore polution","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2009-11-15T09:43:53Z","receivedAt":"2009-11-15T09:43:53Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Sun, Nov 15, 2009 at 12:57:31AM +0100, Sverre Rabbelier wrote:\n\n> I usually compile git from next (sometimes pu to test out a new\n> feature), and when I then switch back to a development branch (usually\n> based off master) I get something like this:\n> \n> $ git status\n> # On branch remote-helpers\n> # Untracked files:\n> #   (use \"git add <file>...\" to include in what will be committed)\n> #\n> #\tgit-http-backend\n> #\tgit-notes\n> #\tgit-remote-hg\n> #\ttest-index-version\n> \n> Now I can easily do 'git clean -f', but it's somewhat annoying. How do\n> other developers deal with this?\n\nI use \"git clean\". :)\n\nThe other option is to mark them for ignore outside of the\nbranch-specific ignore:\n\n  git ls-files -o --exclude-standard >>.git/info/exclude\n\n-Peff\n"},{"id":"127648","messageId":"fabb9a1e0911151622p7863093dn175d2510a88bf268@mail.gmail.com","threadId":"21623","inReplyTo":"20091115094352.GA21477@coredump.intra.peff.net","subject":"Re: .gitignore polution","fromName":"Sverre Rabbelier","fromEmail":"srabbelier@gmail.com","sentAt":"2009-11-16T00:22:41Z","receivedAt":"2009-11-16T00:22:41Z","isPatch":false,"sender":{"key":"srabbelier@gmail.com","avatar":"https://avatars.githubusercontent.com/u/3098?v=4"},"body":"Heya,\n\nOn Sun, Nov 15, 2009 at 10:43, Jeff King <peff@peff.net> wrote:\n> The other option is to mark them for ignore outside of the\n> branch-specific ignore:\n>\n>  git ls-files -o --exclude-standard >>.git/info/exclude\n\nAh, that would work, thanks! :)\n\n-- \nCheers,\n\nSverre Rabbelier\n"}]}