Page 1 of 1

CVS revision/diff

Posted: Thu Sep 22, 2011 12:00 pm
by mazilo
I am much more familiar with SVN and GIT than CVS. In SVN, I can use svn log and svn diff -r PREV to see the latest committed revision and the difference in source codes from the current vs. previous commits, respectively. Similarly, I use git log and git log -p in GIT, respectively. Today, when I did a cvs up ., I noticed there was some new commits. Can anyone here please tell me what CVS parameters I need to use in order to see the latest committed revision and also the difference in source codes from the latest vs. previous commits.

Re: CVS revision/diff

Posted: Thu Sep 22, 2011 12:21 pm
by shorne

Re: CVS revision/diff

Posted: Thu Sep 22, 2011 12:33 pm
by mazilo
Nice, but my preference is to use CVS directly. This way, I can write a simple scripts to do something else.

Re: CVS revision/diff

Posted: Thu Sep 22, 2011 12:42 pm
by shorne
If you are on linux use the commandline
http://www-e815.fnal.gov/webspace/cvs/commands.html

If you are on windows you can use the graphical interface of TortoiseCVS and WinMerge.

Re: CVS revision/diff

Posted: Thu Sep 22, 2011 2:07 pm
by mazilo
shorne wrote:If you are on linux use the commandline
http://www-e815.fnal.gov/webspace/cvs/commands.html
Wow! Looks very interesting that each file has its own revision #. So, is there a way to determine which is current CVS revision of H323Plus after the last commit? The reason I asked this stupid question is because I want to write a small script to package them into a tarball file with a CVS revision #. This way, whenever the script run, it won't overwrite the existing tarball file.

Re: CVS revision/diff

Posted: Thu Sep 22, 2011 11:17 pm
by shorne
Simply store the packages by date/time. You can also update the CVS to particular date/time.

Re: CVS revision/diff

Posted: Fri Sep 23, 2011 3:32 am
by mazilo
shorne wrote:Simply store the packages by date/time. You can also update the CVS to particular date/time.
Thank you.