Producing patches with CVS

[warlord at MIT.EDU (Derek Atkins)]

Tell them to use "patch -p0"

-derek

Christoph Doerbeck A242369 <cdoerbec at cso.fmr.com> writes:

> 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
> 
> _______________________________________________
> Discuss mailing list
> Discuss at blu.org
> http://www.blu.org/mailman/listinfo/discuss

-- 
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
       warlord at MIT.EDU                        PGP key available