cvs commit: src/lib/libc/gen fts-compat.c fts-compat.h
jhb at freebsd.org
Thu Aug 30 15:08:53 PDT 2007
On Wednesday 29 August 2007 04:55:37 pm John-Mark Gurney wrote:
> John Baldwin wrote this message on Mon, Aug 27, 2007 at 15:30 -0400:
> > On Monday 27 August 2007 02:57:41 pm Alfred Perlstein wrote:
> > > Sorry for top posting, but...
> > >
> > > I agree very strongly with Warner, in short, if possible, reducing the
> > > number of major gotchas of running current will make our developer
> > > and early adopters a lot happier.
> > >
> > > It will help FreeBSD.
> > >
> > > One of the things that turns me off to FreeBSD is the feeling that
> > > I get that certain people take some kind of pride in forcing users
> > > to go through dangerous and complex hoops in order to run current.
> > >
> > > It shouldn't be so if the overhead of making it easier is so small.
> > It has zero to do with pride, but it does have a lot to do with allowing
> > to be a branch for development as opposed to the stable branches that are
> > more intended with deployment. Those are quite different feature sets.
> Isn't that what perforce is for?
> Also, we NEED users to be running -current... How many times has a release
> happened and people complained that it didn't get the testing it needed
> to find bug xyz? If we take the attitude that only developers should
> be running -current we'll continue w/ unhappy -stable releases like we
> have in the past...
> Not that Kris doesn't do a great job finding bugs, but other people
> are good at finding bugs too, and we shouldn't lock them out...
How many custom kernels from p4 do you run from other people's branches?
Putting stuff into HEAD is how we get wider exposure for stuff beyond a
developer's own boxes (or a few other people who will test it). We can't
restrict change so much in HEAD that we can't do development there. Also,
for better or for worse, a lot of the peer review kicks in when stuff is
committed to CVS, so churn in HEAD is quite common and it's going to continue
to be there in the future.
More information about the cvs-src