Skip to main content

CVS log Examples - How to get a change log

Recently our team has been committing a lot of files into CVS. We had three branches and were committing files based on certain rules of critical-ness of the commit. After two weeks of such committing, we merged all files to one branch. And then we were asked to give a simple change log for the two weeks. Coming from a strong SVN background, It wasn't easy for me to get a command for this and I have been searching Google, and could not find it. I guess soon we are going to get GITtting, But for now, and for people still adamant to get out of CVS. Here are some samples.

To show the headers of files created after October 1, 2005 and before October 3, 2005:
cvs log -S -d "2005/10/1<2005/10/3"

To show the headers of files in the current directory created after October 1, 2005 through the present time:
cvs log -S -l -d "2005/10/1<now"

Commits by a user with username after a date
cvs log -wusername -S -N -d "<1 Apr 2005"

Note: The quotes and the spacing!

Popular posts from this blog

Powered By

As it goes, We ought to give thanks to people who power us. This page will be updated, like the version page , to show all the tools, and people this site is Powered By! Ubuntu GIMP Firebug Blogger Google [AppEngine, Ajax and other Apis] AddtoAny Project Fondue jQuery

How to Make a Local (Offline) Repository in Ubuntu / Debian

If you are in a place where you dont have internet (or have a bad one) You want to download .deb packages and install them offline. Each deb file is packaged as a seperate unit but may contain dependencies (recursively). apt-get automagically solves all the dependencies and installs all that are necessary. Manually install deb files one by one resolving each dependency would be tedious. A better approach is to make your own local repository. Before you actually make a repo, You need *all* deb files. You dont practically have to mirror all of the packages from the internet, but enough to resolve all dependencies. Also, You have to make sure, you are getting debs of the correct architecture of your system (i386 etc) # 1. make a dir accessible (atleast by root) sudo mkdir /var/my-local-repo # 2. copy all the deb files to this directory. # 3. make the directory as a sudo dpkg-scanpackages /var/my-local-repo /dev/null > \ /var/my-local-repo/Packages # 4. add the local repo to sour...

classpath*: making your Modular Spring Resources

Spring gives multiple options to load XML resources for building contexts. the reference documentation does explain this feature quite well. However, I am taking my shot at explaining the different practical scenarios ( by order of growing modularisation) For Example, A simplest Spring based web Context Loader can be configured with resources like this <context-param> <param-name>contextConfigLocation</param-name> <param-value>applicationContext.xml</param-value> </context-param> <listener> <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class> </listener> You just need to put applicationContext.xml in WEB-INF/ folder of your webapp. However, Typically an application is n-tiered. You can also have multiple files setup and in relative paths. like <param-value> context-files/applicationContext.xml context-files/dao.xml context-files/service.xml </param-value> ...