On Mon, Mar 21, 2011 at 4:45 PM, Michael J Gruber <git@xxxxxxxxxxxxxxxxxxxx> wrote: >> One thing that makes it different from Michael's approach is, :/foo >> will match ':/foo' literally in every directories and foo at top-tree. >> I feel mildly uncomfortable with it, but it makes it consistent with >> other wildcards. If no one objects, I'll try to make a patch with this >> approach. > > Maybe I misunderstand which topic you are referring to. I have a patch > for ":" (to denote repo-root in pathspecs), there's no need to make > another one for ":/". (I would really prefer to do it myself since I > brought it up.) If you make it a wildcard as I mentioned above, the code would be different. Your patch will match only files at top, while wildcards can also match any files literally. You can do it, I don't mind at all. > I was just waiting for agreement to settle in about > which prefix to use. Also, I have checked with J&J of mingw/msysgit fame > meanwhile to make sure that the notation does not create problems on the > windows side of git. The nice (or not) thing about wildcard behavior is that because it would match both cases, we would not need to worry too much. People who don't know the magic can still match files (although more, not less). -- Duy -- 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