On 19/09/2007, David Brown <git@xxxxxxxxxx> wrote: > On Wed, Sep 19, 2007 at 07:23:41PM +0100, Reece Dunn wrote: > > >> I think it would be sufficient to check the first or second character for > >> an 'x'. I'll make a change and give it a try later today. > > > >These are the old file types. If you read the output of `p4 help > >filetypes`, the new way of specifying this is with file type > >modifiers. Therefore, you also have things like text+x. > > So my patch I just sent may not be sufficient. Thing is, we set the file > type as 'text+x' and it comes back as xtext, so I'm not sure if P4 ever > gives out text+x or if that is just available as a new way of specifying > them. I'm not sure. The Perforce help says that xtext and its variants are there for backward compatibility. If you are running an older server with a new client, or the other way around, they may be doing a map from text+x to xtext so that the old version can work properly. This is just speculation, though. I don't know enough to say what Perforce is doing. I find it strange that it is reporting xtext, when you specified text+x. Have you tried a combination that is not supported? Is xunicode supported, in which case you could try unicode+x (if you have a file that you can experiment with)? - Reece - 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
