Subject: Re: Returned mail: see transcript for details
To: None <firstname.lastname@example.org>
From: Shannon Hendrix <email@example.com>
Date: 06/25/2001 19:22:21
On Mon, Jun 25, 2001 at 10:12:32PM +0200, Manuel Bouyer wrote:
> On Mon, Jun 25, 2001 at 11:20:26AM -0400, Shannon Hendrix wrote:
> > On Sun, Jun 24, 2001 at 08:58:26PM -0500, NetBSD list wrote:
> > > Are there any Sparc 5 or 10 (or 20) users out there actually running
> > > the latest kernel code with no on-board SCSI problems?
> > I'm running 1.5.1beta without problems.
> > I didn't mean to do that, but sup seems to have screwed up and put that
> > code in /usr/src/sys, even though my tags for sup say release-1-5.
> 'release-1-5' means the 1.5 release branch, not the 1.5 release itself.
> For 1.5 sources just get the tar archive from NetBSD/NetBSD-1.5/sources/
> No need for sup for a tree which doesn't move any more.
That's not how I thought it worked, and seems counter-intuitive, but it
will do. It seems like there should be a branch for necessary changes to
a release, like bug fixes for example.
If releases are static, then what is the proper way to get bug fixes
for production/stable releases?
For example, things like dhcpd were broken in 1.5, and needed to be
updated on one of my machines. That was my primary reason for starting
to use sup.
I just want the latest version of a release's sources, not the bleeding
edge of a release branch.