Geez. Don't some of you sleep, either?
On Dec 11, at 06:14 AM, Michael Lucas wrote:
>
> > My current plans are to have several patchfiles, grouped by subject (bugfix
> > and/or enhancement), and subordinately grouped by FreeBSD release:
> >
> > ich_sound-patch-4.2REL.udiff delayed_ack-patch-4.2REL.udiff
> > ich_sound-patch-4.3REL.udiff delayed_ack-patch-4.3REL.udiff
> > ich_sound-patch-4.3STA.udiff agp_for_xf86-patch-4.2REL.udiff
> >
> > You get the idea.
>
> <Mr. Burns voice>Excellent</Mr. Burns voice>
Well, as Mr. Watson pointed out, there are better ways, but for an initial
rollout, I don't think that level of sophistication is required.
> Other people will help with QA, if this takes off. Believe me, if a
> patch blows up a system you'll hear about it.
:-)
> > Hey, I'm not taking _anything_ away from y'all; I think all the BSDs are
> > outstanding products. I'm just gonna see if I can't fulfill what I percieve
> > as a support deficiency (again, from my own perspective) in my own little
> > way.
>
> That's the only way anything gets done around here; someone sees a
> need, and fills it. The only question is, is this a need? From
> watching the mailing lists, I certainly think it is.
>
> The point is this:
>
> J D, you have an idea.
"D J", actually. But "Dave" or "Hawk" gets my attention faster.
> Your messages have been read by most of the
> readers of this mailing list. You have gotten a "do it!" from a few
> people, including a -core member. You have gotten a few side comments
> from other developers, such as Matt Dillon's comment on your future in
> the flame wars. So, people have actually read this thread. I might
> be wrong, but I don't believe that you have received a message saying
> "Your idea sucks!" You have also received a few comments on other
> ways this can be handled; this should be taken in the spirit in which
> it is meant, which is "It's a good idea, here's how you could improve
> it."
>
> In FreeBSD, this is what passes for "management buy-in."
>
> So, I officially challenge you: are you going to do it, or is this
> going to wither on the vine like every other time it's been suggested?
> Consider the gauntlet thrown (in the kindest possible manner, mind
> you). Put up an initial patchset, announce it here and on, say,
> daily.daemonnews.org, list an email address for patches on the web
> page, and see what happens.
No challenge necessary. I, too, believe the general attitude is "Go for it.".
So I'm going to. It won't be much to look at initially - maybe ever - but
I'll bring it up and see what happens. It'll take a few days, but I'll post
an "It's here." when it's here. BTW, am I allowed to use the daemon mascot?
I spent some time yesterday browsing cvs-all@, and got another little patch
that backported easily and fixed a nagging problem I've had since day two
(that AGP patch in the above example).
> In fact, if you do it well, you might even find a vaguely well-known
> BSD columnist picking up your site in a future article.
Ack. Don't do that. Sooner or later, the economy will pick up again, I'll
get myself the badly-needed job I lost, and my play-time will once again
be reduced by a factor of four. The last thing I'll need then is any kind
of publicity.
> ==ml
Thanks for all the encouragement and feedback,
Dave
--
______________________ ______________________
\__________________ \ D. J. HAWKEY JR. / __________________/
\________________/\ [EMAIL PROTECTED] /\________________/
http://www.visi.com/~hawkeyd/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
