Forum Discussion

Wolf's avatar
New Contributor
14 years ago

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?

1 Reply

  • tbcooper's avatar
    New Contributor
    The main difference between using addchanges and addcvsdiffs is the amount of metadata you get.  When using addchanges, we connect to the CVS server, and, as a result, are able to get more meta data.  While using addcvsdiffs, you get less metadata because we do not contact the CVS server.

    You are correct that using addchanges will catch the hostname of the
    machine from which the changes are uploaded.  For Perforce and
    Subversion, we have server integration that will allow you to map the machines so that they show as part of the same repository, and that eliminates the issue you are
    seeing.  (For more information on the mapping with Perforce and
    Subversion, see Client Configuration Mapping at 
    With CVS, however, we have no way of pulling out the machine names and thus are unable to map them to one CVS server.  A suggested workaround is to use addcvsdiffs exclusively.