Bug: Local Changes creates incorrect temp files
Hi there, I just discovered a small, probably rarely occurring bug with the Local Changes command. If you run Local Changes on multiple items with the same name, Versions will only generate a temp file for one of them. So for instance, say I have a file setup like this: A/ index.html B/ index.html C/ index.html If I select all the index.html files and then run Local Changes, Versions only generates a temp file (named index.revBASE.html) for the one in the A folder, and then all the index.html files in my working copy get compared to that file instead of their actual BASE versions. I assume this is because Versions tries to use the same temp file name for all the files. Let me know if you need any more details on this bug. Thanks! -Gabriel -- You received this message because you are subscribed to the Google Groups Versions group. To post to this group, send email to versi...@googlegroups.com. To unsubscribe from this group, send email to versions+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/versions?hl=en.
Bug: Double-clicking with multiple files selected only opens one
Double-clicking a file with multiple files selected only opens the one you clicked, rather than all of them. The Open menu command/contextual menu command correctly opens all the files. -Gabriel -- You received this message because you are subscribed to the Google Groups Versions group. To post to this group, send email to versi...@googlegroups.com. To unsubscribe from this group, send email to versions+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/versions?hl=en.
Re: Bug: Local Changes creates incorrect temp files
I have seen something similar on occasion, but it seemed that the filenames got mixed up, so one or more of the FileMerge diffs transformed one document into another. Closing the diff windows and re-issuing the command seemed to fix the problem. It might be a race condition or just not matching up the diff filenames with the full path? It hasn't been a big problem for me, but it's a bug that would be nice to fix for sure. - Quinn On Jan 20, 2010, at 10:47 AM, Gabriel Gilder wrote: Hi there, I just discovered a small, probably rarely occurring bug with the Local Changes command. If you run Local Changes on multiple items with the same name, Versions will only generate a temp file for one of them. So for instance, say I have a file setup like this: A/ index.html B/ index.html C/ index.html If I select all the index.html files and then run Local Changes, Versions only generates a temp file (named index.revBASE.html) for the one in the A folder, and then all the index.html files in my working copy get compared to that file instead of their actual BASE versions. I assume this is because Versions tries to use the same temp file name for all the files. Let me know if you need any more details on this bug. Thanks! -Gabriel smime.p7s Description: S/MIME cryptographic signature
Export ignore
Is there a way to execute an Export but skipping files of a certain type? There are several large files I'd like to just skip, and they're all of a certain type ... ? thanks, -- You received this message because you are subscribed to the Google Groups Versions group. To post to this group, send email to versi...@googlegroups.com. To unsubscribe from this group, send email to versions+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/versions?hl=en.
Subversion in 2010 and Beyond
http://bit.ly/svn2010slides Interesting presentation by Subversion developers Hyrum Wright, Philip Martin, Julian Foad and Dave Brown. Highlights include: HTTPv2.0 This update of the current WebDAV HTTP protocol will boost performance while preserving the benefits of providing web access to Subversion. SVNJ A rich server-side JAVA API that leverages Subversion's established code base. SVNJ will enable the Subversion community to reach out to millions of JAVA developers to create the same rich functionality and extensibility on the server that's available on the client. Obliterate A new feature that cleanly removes obsolete files and other data from Subversion repositories. Obliterate will include comprehensive audit and recovery capabilities to guarantee that history is always available. Working Copy New features include centralized metadata storage and improved extensibility. These enhancements will lay the groundwork for offline commits and other capabilities normally associated with distributed version control systems. -- You received this message because you are subscribed to the Google Groups Versions group. To post to this group, send email to versi...@googlegroups.com. To unsubscribe from this group, send email to versions+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/versions?hl=en.
