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 email@example.com.
There are lots of "cvs commit" made before, and I want to find out which files are affected (or changed) in a particular "cvs commit" happened before. It's very important to know the changes made to the project on the "commit" basis. For example: 1. make some changes to the files 2. cvs ci -m "check in one" 3. make some other changes to the files 4. cvs ci -m "check in two" Now, after step 4, I found something wrong in the code, I would like look back and find out which files I changed in the "cvs ci" command in step 2. "Gerhard Fiedler" <lists at connectionbrazil.com> news:1vae46rq3n8f7.dlg at connectionbrazil.com... > Tom wrote: > >> I would like to examine the check-in to find out which files are changed >> in >> it, but unfortunatelly, I didn't find how to do this. How do you guys >> solve >> this problem? Is there a simple command accomplish this? > > I'm not sure I understand what you want. If you want to examine which > files > are to be committed before they actually are being committed, TortoiseCVS > and WinCvs (and probably most other GUI wrappers) allow this rather > comfortably. > > From the command line, "cvs -q stat -qq" should give you a list of locally > modified files. > > Gerhard