From owner-cvs-sys  Sat Aug 26 13:58:51 1995
Return-Path: cvs-sys-owner
Received: (from majordom@localhost)
          by freefall.FreeBSD.org (8.6.11/8.6.6) id NAA01362
          for cvs-sys-outgoing; Sat, 26 Aug 1995 13:58:51 -0700
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34])
          by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id NAA01342
          ; Sat, 26 Aug 1995 13:58:33 -0700
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id GAA16722; Sun, 27 Aug 1995 06:55:21 +1000
Date: Sun, 27 Aug 1995 06:55:21 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199508262055.GAA16722@godzilla.zeta.org.au>
To: CVS-commiters@freefall.FreeBSD.org, bde@freefall.FreeBSD.org,
        cvs-sys@freefall.FreeBSD.org
Subject: cvsinit doesn't ask about aborting for null log messages
Sender: cvs-sys-owner@FreeBSD.org
Precedence: bulk

I was annoyed when cvsinit didn't prompt for aborting for an empty
log message.  Perhaps it always has always done this, but our log
messages were previously rarely empty because the Submitted by:
(etc.) lines weren't stripped.

What does it do for an empty log message in the middle of a batch?

Bruce