Date: Sun, 30 Oct 2005 17:39:35 -0700 From: Bill Fenner <fenner@research.att.com> To: "Simon L. Nielsen" <simon@FreeBSD.org> Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, Xin LI <delphij@FreeBSD.org>, cvs-all@FreeBSD.org, Andrew Thompson <thompsa@FreeBSD.org> Subject: Re: cvs commit: src UPDATING Message-ID: <200510310139.j9V1dZ3i025712@bright.research.att.com> References: <200510280258.j9S2wpmL058704@repoman.freebsd.org> <20051030194833.GA2699@heff.fud.org.nz> <20051030224106.GC891@zaphod.nitro.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200510310139.j9V1dZ3i025712>