This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

ChangeLog as cvs check-in message


Sorry I put the entire ChangeLog in the check-in message.

Using the ChangeLog as a starting point has its advantages - you
are unlikely to get the wrong entry, and also get a final look at
the ChangeLog you are going to commit.
In this instance, I trimmed away the unrelated entries, then
saw that the date was not updated, went back to fix the ChangeLog,
started the commit again - and then promptly forgot to trim the
log message.

I suppose it is best to automate the ChangeLog reading and pruning so you
don't forget the crucial pruning step.

I've concocted a map line for my .exrc that removes the empty line,
adds a CVS: line at the end, reads in the ChangeLog, trims
out everything beginning with the first date line *after* the first line read,
and changes the trailing blank line into CVS: .
If the leading date line is mine, it deletes that too.
(I sometimes commit patches for people without CVS access, then I put their
 name in the log message.)  If not it deletes the extra CVS: added at the
start.
If it deleted my date line, then an emoty line should be at the start,
so it transforms that into CVS: .

map  :g/^$/d
GoCVS::r ChangeLog
/^[1-9]
:.,$d
:s/^$/CVS:/
?^CVS
/^[1-9].*joern.rennecke@superh.com
dd:s/^$/CVS:

N.B. altough this stuff should be Y10K compliant, it depends on the presence
and exact format of the log entry template and ChangeLog.  If you are
doing something else with your vi-clone editor, it can delete a lot of lines
in your editor buffer.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]