Date: Sun, 30 Oct 2005 18:47:00 -0800 From: Colin Percival <cperciva@freebsd.org> To: Bill Fenner <fenner@research.att.com> Cc: src-committers@FreeBSD.org, cvs-src@FreeBSD.org, cvs-all@FreeBSD.org, Xin LI <delphij@FreeBSD.org>, "Simon L. Nielsen" <simon@FreeBSD.org>, Andrew Thompson <thompsa@FreeBSD.org> Subject: Re: cvs commit: src UPDATING Message-ID: <436585A4.6020008@freebsd.org> In-Reply-To: <200510310139.j9V1dZ3i025712@bright.research.att.com> References: <200510280258.j9S2wpmL058704@repoman.freebsd.org> <20051030194833.GA2699@heff.fud.org.nz> <20051030224106.GC891@zaphod.nitro.dk> <200510310139.j9V1dZ3i025712@bright.research.att.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Bill Fenner wrote: > This happens when there is any commit message that contains the "cvs log" > "end-of-logs" line, [snip] > > 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. Thanks for explaining this -- I've been wondering about it for a long time. Is this something which could be reposurgically corrected? I used to find that cvsweb was very helpful in preparing security advisories, but not any more. Colin Percival
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?436585A4.6020008>