Date: Wed, 21 Feb 2001 18:06:15 -0500 (EST) From: Robert Watson <rwatson@FreeBSD.org> To: "Justin T. Gibbs" <gibbs@scsiguy.com> Cc: Larry Rosenman <ler@lerctr.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/dev/aic7xxx aic7xxx.c aic7xxx.seq aic7xxx_freebsd.c aic7xxx_inline.h aic7xxx_pci.c Message-ID: <Pine.NEB.3.96L.1010221180451.36424A-100000@fledge.watson.org> In-Reply-To: <200102212148.f1LLmqO45391@aslan.scsiguy.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 21 Feb 2001, Justin T. Gibbs wrote: > >And more info for those of us tracking -STABLE only would be useful. > > > >I run Adaptec ctrlrs, and knowing what's being fixed/worked on/ > >broken would be nice. > > The commit log would be identical to that of the commit to -current just > prior. If you filter out -current commit mail because you only run > -stable, you wont get 90% of the relevant info for -stable commits. > MFCs include brief summaries of changes at best. I've found this to be a problem when using cvs log on -STABLE, because often there is no easy way to associated "MFC" as a sole commit message with the respective commit on the -CURRENT branch. It would be nice to have at least a minimal description, or at lack of that, a list of commit versions that are being MFC'd (i.e., MFC: foo.c (1.14-1.18), bar.c (1.67-1.68). Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1010221180451.36424A-100000>