Date: Fri, 09 Feb 2001 17:10:57 -0800 From: Jordan Hubbard <jkh@winston.osd.bsdi.com> To: obrien@FreeBSD.org Cc: Murray Stokely <murray@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/lib/compat Makefile src/lib/compat/compat4x.i386 Makefile libc.so.4.gz.uu libc_r.so.4.gz.uu libdialog.so.4.gz.uu libedit.so.3.gz.uu libfetch.so.2.gz.uu libftpio.so.5.gz.uu libhistory.so.4.gz.uu libncurses.so.5.gz.uu libreadline.so.4.gz.uu ... Message-ID: <23591.981767457@winston.osd.bsdi.com> In-Reply-To: Message from "David O'Brien" <obrien@FreeBSD.org> of "Fri, 09 Feb 2001 15:27:24 PST." <20010209152724.A30856@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> I have stated more than once in the mailing lists why I had yet to make a > compat4x dist. For every 4.x release before 5.0-RELEASE, we now have to > commit new libs. Since they are uuencoded gzip'ed files -- there is zero > lines that remain the same and thus the repo bloat is a big factor. This is simply untrue. The reason we call it "4x" is that it's aimed at the entire branch, not just one release along it, and it's by no means assured that we'll have to commit multiple versions of a single library along the way. I certainly don't recall us updating compat3x with every 3.x release and let's recall our history: You committed the compat3x distribution to the tree on 4/20/1999, just 2 releases into the 3.x-stable branch. We subsequently released 3.2, 3.3, 3.4 and 3.5 on that branch and in all that time you added 3 new libraries, not counting the fortran bits which you simply forgot at the outset. I think your kvetching at Murray is a little overblown here and not very understandable taken in the historical context of your own actions. - Jordan 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?23591.981767457>