On Wed, 16 Jun 1999, Robert Withrow wrote:
>
> dro...@rpi.edu said:
> :- While others seemed too busy with "new" technology to bother with
> :- ugly-old-NFS problems, Matt dived in and pursued them with enough
> :- enthusiasm to make a real difference.
>
> In particular, lots of NFS bugs that ha
dro...@rpi.edu said:
:- While others seemed too busy with "new" technology to bother with
:- ugly-old-NFS problems, Matt dived in and pursued them with enough
:- enthusiasm to make a real difference.
In particular, lots of NFS bugs that had been there, and reported,
since early 2.2 days. Bugs th
> For the benefit of those of us who weren't at USENIX, can we please
> have a summary of what was discussed/decided?
Nothing was [deliberately] decided but much was discussed. As soon as
one of us lands back home in some reasonable state, a summary will be
posted. I've yet to do this myself and
Jordan K. Hubbard wrote:
> Excellent. Let's assume then that all the core folk who are there,
> plus any committers who have an interest in the issue (since core has
> to listen to its developers' opinions too or we can no longer honestly
> claim to represent their interests), will be getting toge
>
> For what it's worth, and to throw another hat into the fray, it
> seems to me that two things are driving the tension here:
>
> 1)Matt is effectively in a position where he no longer has
> to work, and can now dedicate a significant amount of
> focussed effort over long interv
For what it's worth, and to throw another hat into the fray, it
seems to me that two things are driving the tension here:
1) Matt is effectively in a position where he no longer has
to work, and can now dedicate a significant amount of
focussed effort over long intervals at F
Jason Thorpe wrote:
> I dunno, John. Matt's right on the ball here, from my experience. Vague
> non-answers seem to be your specialty.
That appears to be a comment designed to create a flame war. It certainly
is not helpful to FreeBSD. Please don't abuse our lists.
--
John Birrell - j...@cimlo
> On Sat, 5 Jun 1999 03:24:07 -0500 (EST)
>
> > The frustration that I was showing was a result of off the wall assertions
> > being made, with few coherent questions. Your questions are often
> > analogous to someone saying that the VM code sucks, but will you help me
> > with it, by teachi
On Sat, 5 Jun 1999 03:24:07 -0500 (EST)
"John S. Dyson" wrote:
> > I don't want to be a pest, because this really shouldn't be on an
> > open forum. But John: I would ask you questions and the answers I
> > would get would be in the form: "Nobody understands that
> > cod
Matthew Dillon said:
>
> I don't want to be a pest, because this really shouldn't be on an
> open forum. But John: I would ask you questions and the answers I
> would get would be in the form: "Nobody understands that
> code but me, don't touch what you don't understand", or "T
On 04-Jun-99 Chuck Robey wrote:
> On Thu, 3 Jun 1999, Vince Vielhaber wrote:
>
>> > Just realize, IF you're loud enough, and succeed, the programmers will
>> > all desert you, and you'll have a nice place to argue, but no more
>> > software. Core here does an excellent job, with all the problems
On Thu, 3 Jun 1999, Vince Vielhaber wrote:
> > Just realize, IF you're loud enough, and succeed, the programmers will
> > all desert you, and you'll have a nice place to argue, but no more
> > software. Core here does an excellent job, with all the problems they
> > face, most committers will agr
:The learning curve would have been much less painful if questions
:would have been asked and/or the answers weren't ignored. (There were
:cases of my answers and suggestions not even being challenged, but
:were rejected out of hand.) After a while, the *only* way to be
:heard was to become extre
[.]
> Someone who has this much spare energy for tracking down ancient
> problems in technologically-uninteresting code should be getting
> some reward for it. In a project like this, it seems to me that
> the standard reward is a certain degree of respect, and I think
> Matt's recent work has
Chuck Robey wrote:
> [I rearranged the things since these folks can't be bothered to comment
> at the bottom]
>
> > Vince Vielhaber wrote:
>
> > > Not knowing the FULL story from both sides, I feel it'd be inappropriate
> > > if I were to comment on it. However knowing Matt's coding abilities,
Nate Williams said:
>
> Case in point, John Dyson's comments explanation to the mailing list for
> many of his design decisions explained to even an uninformed person like
> me that some of the changes you've made were penalizing FreeBSD, not
> helping it in some cases.
>
BTW, my frustration was
On 04-Jun-99 Chuck Robey wrote:
> [I rearranged the things since these folks can't be bothered to comment
> at the bottom]
>
>> Vince Vielhaber wrote:
>
>
>> > Not knowing the FULL story from both sides, I feel it'd be inappropriate
>> > if I were to comment on it. However knowing Matt's codin
[I rearranged the things since these folks can't be bothered to comment
at the bottom]
> Vince Vielhaber wrote:
> > Not knowing the FULL story from both sides, I feel it'd be inappropriate
> > if I were to comment on it. However knowing Matt's coding abilities,
> > having seen the eruption here
On 03-Jun-99 Amancio Hasty wrote:
> It is a nice idea and I have proposed it in the past however most likely
> such organization will devolve to the current status-quo with core;however,
> if the oversight committee is composed of individuals from companies
> using FreeBSD it may actually work for
It is a nice idea and I have proposed it in the past however most likely
such organization will devolve to the current status-quo with core;however,
if the oversight committee is composed of individuals from companies
using FreeBSD it may actually work for committee should have a vested
interest i
On 03-Jun-99 Jaye Mathisen wrote:
>
> I second this. Even if it's a bit painful, somebody who has been working
> diligently at this needs to be able to be make their work usable quickly.
> I would guess that not too many things hinder progress, or quash desire
> more than fixes to problems langu
I second this. Even if it's a bit painful, somebody who has been working
diligently at this needs to be able to be make their work usable quickly.
I would guess that not too many things hinder progress, or quash desire
more than fixes to problems languishing.
There has to be some middle ground s
At 2:08 PM -0700 6/3/99, Jordan K. Hubbard wrote:
> Excellent. Let's assume then that all the core folk who are there,
> plus any committers who have an interest in the issue (since core
> has to listen to its developers' opinions too or we can no longer
> honestly claim to represent their interes
Excellent. Let's assume then that all the core folk who are there,
plus any committers who have an interest in the issue (since core has
to listen to its developers' opinions too or we can no longer honestly
claim to represent their interests), will be getting together during
the week to discuss t
:Perhaps we can cut through all the finger pointing and counter-finger
:pointing here and just move on to the chase by asking one simple
:question: Will you be at USENIX? That would be an excellent
:opportunity to discuss it in person, where emotion and
:facial-expression stripping isn't such a hu
Perhaps we can cut through all the finger pointing and counter-finger
pointing here and just move on to the chase by asking one simple
question: Will you be at USENIX? That would be an excellent
opportunity to discuss it in person, where emotion and
facial-expression stripping isn't such a huge pr
:Matthew Dillon writes:
:
:> I have to say, though, that in order to fix these bugs I really do
:> need my commit privs back. If people want these things fixed,
:> complain to core. I have the time to fix the bugs with commit
:> privs, but I just don't have the time or inclinatio
> > I have to say, though, that in order to fix these bugs I really do
> > need my commit privs back. If people want these things fixed,
> > complain to core. I have the time to fix the bugs with commit
> > privs, but I just don't have the time or inclination to fix them
> > w
[
Some history: I'm not a core member (I gave that up responsibility years
ago), but I was one of the three weirdo's that started up FreeBSD back
when I had no life. My opinions are my own, and don't reflect the core
team. I don't know the exact reasons why the core team removed Matt's
commit pri
29 matches
Mail list logo
