i would suggest two trees simply for backup purposes. but if the source is so easily available (small tarball, few files, short download...) i don't see the point. in the VBA world, we always made a backup of the working version before starting to mangle, patch, and/or crunch the code.
if you're making a diff patch, two trees may be the best way to do it, but i'm not an expert on diff... if you're simply going to build a new tarball with your patch included, AND the source is easily available, one tree should be plenty. moral : keep backups! $.02 --- Rob Hudson <[EMAIL PROTECTED]> wrote: > If there is a piece of software that I want to make a patch on, how > does one do this? Do you need 2 trees - the original and the changed > one? > > Thanks, > Rob > -- > Rob <rob_at_euglug_dot_net> > my @euglugCode = qw(v+++ e--- eug+ bsd+++ gnu+ S+++); > ===== Justin Bengtson @euglug=(v+ e- eug++ bsd? gnu++ s++) [EMAIL PROTECTED] "i called some kid 'b' the other day. it's the price you pay for living hip-hop every day of your life." Jerry (from the Point Blank Rangers) __________________________________________________ Do You Yahoo!? Yahoo! Greetings - Send FREE e-cards for every occasion! http://greetings.yahoo.com
