Re: Maintainer policy for GDB

Eli Zaretskii
2005-11-18T18:24:46Z

> Date: Fri, 18 Nov 2005 10:26:18 -0500
> From: Daniel Jacobowitz <drow@false.org>
>
> I don't think the words are at all similar in semantic meaning.
> Responsibility is an obligation and authority is a privilege.

What I meant was that the expression of their meaning is similar: it's
who reviews patches, right?

> This would be easier with Venn diagrams, but they don't lend themselves
> to email very well. Let me give some examples. Afterwards, I will
> attempt to clarify the original descriptions, if these help.

Sorry, I must be too dumb today. In the example you've given, who has
the ``authority for reviewing patches''?

> > Isn't it desirable to have an expert for each area of GDB code? If
> > not, why not? what are the disadvantages of that? (I don't think this
> > is directly related to the present discussion, but I was too surprised
> > to read your negative response to Joel's question to let that go
> > without understanding it.)
>
> Perhaps we're just using "goal" differently.

Probably. Thanks for explaining what you meant.