Re: [antlr-dev] Ummmmmm Perforce? Wow...

[Jim Idle]

Sam Harwell wrote: Lets you check in a folder and a file with the same name?   How can I make it not allow a particular file to ever be checked in (exclusion by name)? Read up on triggers. I tried checking in a folder with the same name as the file, then deleting it from disk and putting a file there instead, and it let me check in that file without even a warning. Well, perforce does not check in folders, it checks in files within folders. Presumably if you delete a file, then you don't want it it any more other than in history, so why should it stop you checking in a folder that happens to be the same name as folder you have deleted, or vice versa. I think you are thinking to much svn/hg/git and all the other crummy attempts (IMO of course ;-). You can sync anything to any revision and if you try to sync over something then you will get a warning. The system works to preserve the current file revisions on your disk, not prior versions, unless you ask for prior versions. Having being forced to use every SCCS known to man, over the last xx years, I can tell you that perforce kicks everything else into touch. You do of course need to get to know it and the gestalt of it. Jim

_______________________________________________
antlr-dev mailing list
antlr-dev@antlr.org
http://www.antlr.org/mailman/listinfo/antlr-dev