[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: diff in commit message (was: Multiple-line log message)

From: Richard J. Duncan
Subject: Re: diff in commit message (was: Multiple-line log message)
Date: Tue, 24 Oct 2000 14:21:47 -0500 (CDT)

> On Mon, Oct 23, 2000 at 14:59 -0500, Giang, Richard P wrote:
> > 
> > Does anyone know how to enter a log message that expands
> > multiple lines using command line cvs commit -m?
> Does anyone know a method how to incorporate "cvs diff" into the
> "cvs commit" message and thus aid the committer with showing what
> has changed when he is asked to specify what he did and why?
> As a background:  At the moment I employ a homegrown wrapper
> script around RCS to catch the diff before invoking an editor
> with the diff log and the "tell me why you did it" message.
> I tried to accomplish something similar in CVS, but failed
> miserably. :(  The rcsinfo is too static (updated only with "cvs
> update", not referenced when -m is specified).  Setting an
> CVSEDITOR pointing to a script to invoke "cvs diff" and "$EDITOR"
> hangs due to the lock already set by "cvs commit".  So I realized
> I had to fiddle with the source and narrowed it down to commit.c
> at a time where start_server() is done but do_editor() is not
> yet.  That's where I would catch the diff output and append it to
> the saved_message.

I think hacking the source is overkill.

Your locking problem can be solved by running diff with the -n option
(proceed without lock).

Do you want to see the diff output to assist in typing the "this is
what I did" message? If not, consider using the loginfo file. I think
the commitinfo or editinfo files can help if you want it in the editor
window, but I haven't done this personally.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]