I just has the following use case: I have the lazarus.lpi project opened in the IDE and the SVN plugin is configured to use my local working copy lazarus/trunk/ for this project. I have made a change to a file in the components/ folder which does *not* belong to the lazarus.lpi but still is part of trunk/ and part of the same repository. Although the file does not belong to the lazarus.lpi I have simply opened it as a new tab in the source editor out of pure lazyness.
When trying to view the diff to base it will tell me that the file does not belong to the project (this is correct) and refuse to show me the diff (this is bureaucratic bullying). If I select "commit" from the menu (only to see the list of files) it will be displayed as a changed file and from there I can view the diff (and probably even commit it) without problems. Only diretly from the menu it is not allowed. Is this restriction really necessary? shouldn't it just do "svn diff filename" and let svn figure out on its own whether this makes sense or not and completely ignore whether the file is actually a pascal unit referenced from the currently opened .lpi or is just some other arbitrary file that is version controlled but not a unit of the current proect? Of course I could have closed lazarus.lpi and opened the project in the components folder and then associate this also with the same working copy and activate it and from there it would have allowed me to see the diff but what is with files that are not part of any lazarus proect (a simple readme file for example) but still belong to the repository? I feel that this restriction can simply be removed since "svn diff" can not do any harm and it can be circumvented anyways by simply doing the same diff in the commit dialog instead. Bernd -- _______________________________________________ Lazarus mailing list [email protected] http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
