From owner-freebsd-hackers Tue Jan 24 09:02:58 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id JAA01904 for hackers-outgoing; Tue, 24 Jan 1995 09:02:58 -0800 Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id JAA01898 for ; Tue, 24 Jan 1995 09:02:56 -0800 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.9/8.6.9) id JAA24550; Tue, 24 Jan 1995 09:02:44 -0800 Date: Tue, 24 Jan 1995 09:02:44 -0800 Message-Id: <199501241702.JAA24550@silvia.HIP.Berkeley.EDU> To: terry@cs.weber.edu CC: hackers@FreeBSD.org In-reply-to: <9501241622.AA12124@cs.weber.edu> (terry@cs.weber.edu) Subject: Re: cvs commit From: asami@cs.berkeley.edu (Satoshi Asami) Sender: hackers-owner@FreeBSD.org Precedence: bulk * > cvs commit said something like "ci warning: missing message for -m * > option" and started asking for messages using the ">>" prompt after * > I typed "!" in response to the "a)bort, c)ontinue, e)dit, !)reuse this * > message unchanged for remaining dirs" question during a * > multi-directory commit. Anyone know why? * * I have always seen this on multidirectory commits. What happens is the * message is created in the first subdirectory, since each directory is * the current directory for the commit phase. * * Typically, if the changes you made are all described by your first comment, * use the '!' to reuse the comment on all files. I know.... Sorry if it wasn't clear, the problem is that it DIDN'T re-use the message after my "!", printed out the message ("ci warning") given above and then resorted to ">>" prompts (the one you get on vanilla ci operation...I think) for the remaining files. Anybody else having problems with multi-directory commits? Satoshi