ContributionsMost RecentMost LikesSolutionsRe: Recent git changes in Code CollaboratorI'm humming Pink Floyd's "Is there anybody out there?" in my head now....Recent git changes in Code CollaboratorWe're running Code Collaborator version 6.5.6505 Support pages mention improvements in git support in the newest versions. What differences are there in git support from 6.5.6505 to the latest code collaborator? I could not find much discussion or notes on this.bug with "next difference" after "compare" menu usedWe're running Code Collaborator 6.0.6012 with mostly C,C++, and Perl code. After viewing the changes for a file in the file overview sub-window and then using the compare menu to select any combination of files (including the original and/or only two files shown) the "next difference" and "previous different" buttons (just to the right of the compare menu button in the top taskbar) no longer know where any differences are and always say "you have reached the end of the file, would you like to start from the beginning", even when one can see differences shown on the screen, and even if it just said that the last time you clicking the button. Clicking the same "next/previous difference" button more than once just keeps saying the same "end of file reached" message. This bug is repeatable. Has it been fixed in a later release? This is a potentially serious bug because some users have reported missing changes because the "next difference" button did not show them anything, approving the changes without realizing they are there. change set includes hostnames? why?We switched to using VM login hosts, meaning user may log into different host on different days, and we found an unusual behavior. All our developers upload their changes from a linux commandline using then ccollab client. But some of them use the addcvsdiffs method, and some use the addchanges method. Those using addchanges noticed that the hostname is part of the change set, and if they get a different VM and try to upload further changes to the review, the files end up in a second change set showing the different hostname, rather than using the file path to identify them as the same file like an addcvsdiff does. So what is really the difference between addchanges and addcvsdiffs (since they look the same during a simple review) and why is the hostname part of the addchanges change set? And is there a way to turn it off so it doesn't consider the hostname when uploading changes?