On Sat, Feb 07, 2009 at 01:33:43AM +0000, Sitaram Chamarty wrote: > > I think it might be useful to be able to get this information. However, > > rather than coupling it with "git add", it might make more sense to have > > a separate way to query "is this being ignored, and if so, by what > > pattern". Then you could use that tool to generally debug your > > .gitignore patterns. > > maybe GIT_TRACE could print that as well, in some way? It could, but I think reusing GIT_TRACE isn't a good idea. Currently it traces _just_ exec information, so I wouldn't want to pollute that with this information. But yes, you could trigger it through an environment variable, which would let us dump at the lowest level. I spent a few minutes checking this out, and it looks to be a little more complex than I had hoped, just because we don't have all of the information in the same place at the same time. A toy patch series follows; see 2/2 for a description of why it doesn't work like you might hope. I'm not too interested in trying to deal with the refactoring that would be required to do it right. But maybe somebody else is. -Peff -- 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
