Johannes Luber wrote:
However it does not stop you doing it as it detects that you have overwritten a file. Also, the files are read only when not checked out, so the only way you can overwrite is to do so deliberately. If you try to save and are told that the file is read only, then you have a few options: 1) Just check it out now, then save it. 2) Save it, then check it out - perforce won't overwrite your work. The model is much better, as the server knows what is going on, which means others know what you have checked out.But if you are used to not checking things out, it seems surprising is all. Not sure what you mean here or what IDE you are using (or command line? Windows? UNIX?). You know about p4v right? p4 filelog? p4 help?Furthermore I have to lose the current history view, which forces me to remember the current changeset during the edits and not just between edit sessions. Errr, no they don't and yes you can. Have you read the manual? FAQs and so on? Perforce tracks revisions and branches WAY better than anything else. You just have to specify that you want it to follow branches if you want it to. Again, p4v will help you here.Another problem is the abyssmal handling of moved files. They lose their history and one cannot diff between a changeset before the move with one afterwards. Well, it has better documentation; it will help you to read through it a bit if you are going to develop with it. Basically, if you find yourself doing things awkwardly with perforce, like you are suggesting above, then you are missing something. Like any tool, knowing more about it will help you and mainly knowing where to look to ask/find the question is what you want. p4 changes -iSo you have to change the revision number manually. Even subversion does here better. Please tell me, where Perforce has its superiosity compared to other SCMs. Jim |
_______________________________________________ antlr-dev mailing list [email protected] http://www.antlr.org/mailman/listinfo/antlr-dev
