From: Eli Zaretskii <eliz@gnu.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb-patches@sourceware.org
Subject: Re: [commit] Mention VAX floating-point support in NEWS
Date: Wed, 02 Nov 2005 04:32:00 -0000 [thread overview]
Message-ID: <uirvb8yhh.fsf@gnu.org> (raw)
In-Reply-To: <20051101205628.GA4668@nevyn.them.org> (message from Daniel Jacobowitz on Tue, 1 Nov 2005 15:56:28 -0500)
> Date: Tue, 1 Nov 2005 15:56:28 -0500
> From: Daniel Jacobowitz <drow@false.org>
> Cc: Mark Kettenis <mark.kettenis@xs4all.nl>, gdb-patches@sourceware.org
>
> On Tue, Nov 01, 2005 at 09:54:17PM +0200, Eli Zaretskii wrote:
> > > Date: Tue, 1 Nov 2005 08:31:28 +0100 (CET)
> > > From: Mark Kettenis <mark.kettenis@xs4all.nl>
> > >
> > > Thought this was worth mentioning.
> >
> > It is, IMO.
> >
> > > Committed,
> >
> > Whatever happened to the custom to ask whether there are any
> > objections, or even (gasp!) make it an RFA? NEWS is not one of the
> > files for which you are the responsible maintainer, and neither is
> > this change obvious, IMHO.
>
> >From gdb/MAINTAINERS:
>
> NEWS ALL
I don't know what this means, exactly (and MAINTAINERS doesn't
explain). The practice until now was that changes to NEWS _were_
discussed.
Anyway, I think, after what's happened lately, we should try to err on
the side of more cooperation and collective decisions, not less.
> In any case, I don't see why additions to NEWS should require any more
> approval than the feature they're describing. Why isn't it obvious?
It's not obvious because not every change we make goes into NEWS.
next prev parent reply other threads:[~2005-11-02 4:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-01 7:31 Mark Kettenis
2005-11-01 19:54 ` Eli Zaretskii
2005-11-01 20:56 ` Daniel Jacobowitz
2005-11-02 4:32 ` Eli Zaretskii [this message]
2005-11-01 21:22 ` Mark Kettenis
2005-11-02 4:40 ` Eli Zaretskii
2005-11-01 23:00 ` Joel Brobecker
2005-11-02 5:18 ` Eli Zaretskii
2005-11-02 5:55 ` Joel Brobecker
2005-11-02 20:34 ` Eli Zaretskii
2005-11-02 23:00 ` Jim Blandy
2005-11-02 23:04 ` Daniel Jacobowitz
2005-11-03 1:34 ` Jim Blandy
2005-11-03 6:58 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=uirvb8yhh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox