On Sun, May 11, 2008 at 5:44 PM, Paul Moore <[EMAIL PROTECTED]> wrote: > 2008/5/11 Alexandre Vassalotti <[EMAIL PROTECTED]>: >> When I rename a module I use "svn copy", since "svn remove" doesn't >> pick up changes made to the "deleted" file. For example, here is what >> I did for PixMapWrapper: >> >> svn copy ./Lib/plat-mac/PixMapWrapper.py ./Lib/plat-mac/pixmapwrapper.py >> edit ./Lib/plat-mac/PixMapWrapper.py >> svn commit > > That seems a very odd usage. You're renaming, not copying. Why aren't > you using svn rename (svn move)? I can well imagine this causing > serious confusion. >
I wrote: > When I rename a module I use "svn copy", since "svn remove" doesn't > pick up changes made to the "deleted" file. For example, here is what > I did for PixMapWrapper: Oops, I meant "svn rename" when I said "svn remove". As I said, if I use "svn rename" I cannot make changes to the file being renamed. > Please be very careful here - if you introduce revisions which contain > multiple files with names that differ only in case, you're going to > really mess up history (and probably the only clean way to fix this > will be to actually go back and edit the history). Oh, you are right. I totally forgot about case-insensible filesystems. This is really going to make such case-change renamings nasty. -- Alexandre _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
