Hey Peff, I actually have an issue with the behavior we discussed (referenced as 1.A.) Using the example from Michael's mail, I end up having this: $ git status --porcelain --ignored ?? .gitignore ?? x ?? y/ !! x.ignore-me !! y/ y/ is referred as untracked, because it contains untracked files, and then as ignored because it contains ignored files. Showing it twice doesn't feel right though, so I guess we should only show "?? y/" with untracked=normal, and "!! y/foo.ignore-me" when using untracked=all What do you think ? On Thu, Dec 27, 2012 at 6:35 PM, Antoine Pelisse <apelisse@xxxxxxxxx> wrote: >> By "committed", I assume you meat that you have "dirA/unco" as an >> untracked file, and "dirA/committed" as a file in the index? > > Of course, > >> Thanks for putting this together. I agree with the expected output in >> each case, and I think this covers the cases we have seen (case 1 is >> Michael's original report, case 2 is what I wrote in my mail, and case 3 >> is the one you just came up with). I can't think offhand of any others. > > Great, so I can build some tests reflecting those behaviors while > waiting more inputs -- 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