Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Producing patches with CVS

Hey folks,

I have a project I work on and it's kept in CVS on my local server.  Up
to this point, I have always committed all recent changes, tagged
the commit, and built a giant tar ball to release the newest code base.
This required that anyone who is playing with my software constantly
do an upgrade.  Now I'm hoping to start doing interim patches.

Initially, I was hoping that something like this would work:

	cvs diff -c -r "last-release" -r "todays-release" > patch.diff

and then someone who installed my stuff could simply

	cd install-dir
	patch < patch.diff

Howerver, that starts prompting for filenames to patch, and even though it
it works... it's not very glamourous.

Are there handy tools (like makepatch) that work well with CVS?  Or maybe
I'm just not using the right options (context vs. uni diff crap)...

All comments/suggestions welcome.

- christoph

BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!

Boston Linux & Unix /