cvs commit: src UPDATING

[Bill Fenner]

This happens when there is any commit message that contains the "cvs log"
"end-of-logs" line, e.g.,

----------------------------
revision 1.342.2.13
date: 2004/10/10 16:16:31;  author: mtm;  state: Exp;  lines: +14 -5
branches:  1.342.2.13.2;
RCS file: /home/ncvs/src/UPDATING,v
----------------------------
revision 1.372
date: 2004/10/07 14:51:23;  author: mtm;  state: Exp;  lines: +0 -0
Make a note in UPDATING about the recent change regarding
the FreeBSD keyword.
=============================================================================

o Add additional information on how to cope with this change.
o Fix the date for the previous libthr change to correctly reflect
  the date it was MFCed on.

Approved by: re/assumed because of approval for the actual src change
----------------------------

This is a single entry, but there's no way to know that just
parsing this output.

cvsweb could just wait for eof, and not try to use the ===== line to
mark the end, but that would result in some more confused states since
it'll have two records of revision 1.372.

As I mentioned in another context, this has been on my todo list to
fix for almost 10 years.

  Bill