From owner-cvs-usrsbin Tue Apr 9 14:10:54 1996 Return-Path: owner-cvs-usrsbin Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA14304 for cvs-usrsbin-outgoing; Tue, 9 Apr 1996 14:10:54 -0700 (PDT) Received: from grumble.grondar.za (grumble.grondar.za [196.7.18.130]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id OAA14267 Tue, 9 Apr 1996 14:10:36 -0700 (PDT) Received: from grumble.grondar.za (mark@localhost [127.0.0.1]) by grumble.grondar.za (8.7.5/8.7.3) with ESMTP id XAA02292; Tue, 9 Apr 1996 23:09:11 +0200 (SAT) Message-Id: <199604092109.XAA02292@grumble.grondar.za> To: "Marc G. Fournier" cc: "Marc G. Fournier" , CVS-committers@freefall.freebsd.org, cvs-all@freefall.freebsd.org, cvs-usrsbin@freefall.freebsd.org Subject: Re: cvs commit: src/usr.sbin/cron/crontab crontab.c Date: Tue, 09 Apr 1996 23:09:06 +0200 From: Mark Murray Sender: owner-cvs-usrsbin@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk "Marc G. Fournier" wrote: > Can someone tell me how to actually put this into -stable as > well? Everyone makes it look like such a simple thing to do, but > I don't presume that its a simple matter of 'cvs commit -r RELENG_2_1_0'? > I would assume I'd have to checkout the 2.1.0 version, then install the > patch and then commit again? The easiest is for you to checkout STABLE and repatch: $ cvs co -rRELENG_2_1_0 crontab $ cd crontab $ patch < ...... $ cvs commit The -rBLAH is 'sticky', so you only need it on the co. Under the right circumstances (not too many diffs), you could replace the patch step with something like $ cvs update -jHEAD some_file.c And review the diffs with "cvs diff" M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 Finger mark@grondar.za for PGP key