From owner-cvs-usrbin Tue Jul 1 02:01:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA19732 for cvs-usrbin-outgoing; Tue, 1 Jul 1997 02:01:38 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (ala-ca19-01.ix.netcom.com [205.187.212.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA19497; Tue, 1 Jul 1997 01:57:18 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.6/8.6.9) id BAA01753; Tue, 1 Jul 1997 01:51:24 -0700 (PDT) Date: Tue, 1 Jul 1997 01:51:24 -0700 (PDT) Message-Id: <199707010851.BAA01753@silvia.HIP.Berkeley.EDU> To: obrien@NUXI.COM CC: cvs-committers@freebsd.org, cvs-all@freebsd.org, cvs-usrbin@freebsd.org In-reply-to: <19970701014441.47488@dragon.nuxi.com> (obrien@NUXI.COM) Subject: Re: cvs commit: src/usr.bin/file/Magdir alpha amanda amigaos asterix digital island mach osf1 sniffer xenix From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-cvs-usrbin@freebsd.org X-Loop: FreeBSD.org Precedence: bulk * I did a cvs tag operation to bring these files into 2.2-STABLE. * And since tag operations don't generate commit messages, I did a "forced" * commit after the tag. I see. It may have been better if you said just that in the commit message though. :) * Bad idea? No, but the new cvs allows you to "cvs add" files into branches directly so I think that is the recommended method now. (It lets you enter commit messages too.) Satoshi