Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
"Arthur Barrett" <arthur.barrett at march-hare.com> wrote in message news:fod1ia$o5r$1 at paris.nodomain.org... >> What I mean by this, is in CVS, I find myself checking in files one at a >> time so I can have proper log history as to what has changed between file >> iterations. This works really well for me when looking through history >> and helps to know which files to select for comparison purposes, but it >> doesn't let me know which set of files are all related to the same >> commit. The only way around this so far, has been to select all related >> files for a single commit, and then to go back and add to each file's log >> msg individually. > > CVSNT and EVS both support this, use "cvs ci -B 1234" where 1234 is the > changeset number. The changeset number can even be used in a merge... True - I had forgotten about that. I guess I've never really used that option as it is only available in Tortoise (I mostly use WinCVS). I don't believe that WinCVS supports it in the interface, does it? The Eclipse integration definitely does not. I guess it is really more of an issue for the client tools to support the options better.