I did find out what problem was. Since I was using vim (or gvim) which
forked out a separate window, for some reason CVS assumed I had completed
typing the log message, even before I actually typed in anything. So now vim
does not fork out a separate process.
Not sure if this is a bug or not, but I am posting it in the cvs.bug group.
"Steve Greenland" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> On Wed, Dec 19, 2001 at 12:21:34PM -0500, Jeremiah wrote:
> > I am using CVS on HP-UX 11.00. I use CVS in the bash shell. The CVS
version
> > is 1.10.8. When I cvs commit a file, it brings up the vi editor and asks
me
> > to put my comments in, which I do. Then it prompts me saying that the
log
> > message is empty and if I want to continue or not. Why is not the log
> > message being accepted? Do I need to do somekind of setup?
>
> Possibilities:
>
> 1. You're not saving the file. Use ":wq", not ":q!". ;-)
>
> 2. Are you using a version of vi (or have you enabled an option) that
> creates backups by moving the original and then writing a new version?
> Depending on how the CVS tracks that file, it may not see the new
> version. Turn that option off.
>
> Steve
>
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
