Date: Tue, 11 Dec 2001 18:58:47 +0200 From: Alexey Zelkin <phantom@FreeBSD.org> To: Josef Karthauser <joe@tao.org.uk> Cc: Peter Wemm <peter@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/gnu/usr.bin/binutils/gdb/i386 kvm-fbsd.c Message-ID: <20011211185847.A99187@ark.cris.net> In-Reply-To: <20011211164118.B27214@tao.org.uk>; from joe@tao.org.uk on Tue, Dec 11, 2001 at 04:41:18PM %2B0000 References: <200112110704.fBB74mk31239@freefall.freebsd.org> <20011211164118.B27214@tao.org.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
hi, On Tue, Dec 11, 2001 at 04:41:18PM +0000, Josef Karthauser wrote: > > peter 2001/12/10 23:04:48 PST > > > > Modified files: > > gnu/usr.bin/binutils/gdb/i386 kvm-fbsd.c > > Log: > > (null) > > Is it worth having the commit fail if there's a null log message? It could be useful as for me. But make sure that it should work correctly in both pserver and local modes. In pserver mode it's not a problem to check for null commit log and fail since all files are comiting at once, but in local mode following scenario may exists: . hack files in few directories . do cvs commit . write correct log for first directory files . emptify log for second directory in this case scripts will fail to continue and don't send email with "(null)" content, but patches for first directory are already applied. As result we have complete commit (at least part) and no notification sent. PS: What about fix with current "$FreeBSD$ line mungled" CVSROOT problem ? Bunch of patches from my tree awaiting to be commited! :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011211185847.A99187>