On Fri, Dec 7, 2012 at 6:50 PM, Matthew Ciancio <matthew.ciancio16@xxxxxxxxx> wrote: > Imagine this scenario: > > 1) You have a Git repo with two branches (branchA and branchB), which are > currently identical. > 2) Checkout to branch. > 3) Create file foo.txt, stage it and commit it. > 4) Create file ignore.txt and add it to the ".gitignore" file of branchB so > that it is successfully ignored by Git. > 5) Checkout to branchA. > > Problem: ignore.txt does not "disappear" like foo.txt does When you say "disappear", do you mean "deleted from the file system" or something else? > and is now just > sitting in branchA (and now any other branch I checkout into). It's not in branchA, it's just no longer ignored because your changes to .gitignore were effectively reverted by jumping back to the commit that branchA points to. > When I first started using Git, I genuinely thought this was a bug, because > it seems so logical to me that ignore files should hide/reappear just like > tracked files do, when switching branches. "hide/reappear" is the equivalent to saying "deleted/created" in the case of a tracked file in your working tree. But how would Git cause an untracked file to reappear? By definition, it doesn't know anything about the file. > P.S. Here is a forum post I made on StackOverflow about the issue: > http://stackoverflow.com/questions/13761682/gitignore-hide-ignored-files-dur > ing-checkout I posted an answer there, too, but I'm not sure I fully understand the problem. The top-voted answer doesn't make much sense, though. Thanks, Chris -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html