Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@redhat.com>
Cc: brobecker@adacore.com, gdb-patches@sourceware.org
Subject: Re: RFA: fix PR python/11792
Date: Wed, 22 Sep 2010 19:59:00 -0000	[thread overview]
Message-ID: <83vd5xvaep.fsf@gnu.org> (raw)
In-Reply-To: <m3zkv97flm.fsf@fleche.redhat.com>

> From: Tom Tromey <tromey@redhat.com>
> Cc: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
> Date: Wed, 22 Sep 2010 13:17:25 -0600
> 
> >>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
> 
> Eli> Yes.  We are also supposed to humor the responsible maintainer when
> Eli> she asks for some simple change as part of the review process.
> 
> That is no reason to ignore the agreed-upon rules.

It is to me.  The agreed-upon rules are a two-way street, you know.
If people are not interested to see the manual fit the quality
standards that I consider important (which aren't much, if you follow
my reviews), I don't see why they should be interested in seeing my
patches to fix that what they declined to.  Not to mention the fact
that every commit is visible after you resync with the repository,
anyway.

> In this case I did not read your message as a request.  I saw it as a
> conditional suggestion, which I chose not to take.

I don't see any difference between a suggestion and a request, when it
comes from the responsible maintainer.  And I don't see a difference
between "chose not to take" and "decline to" (a.k.a. "refuse").  I'm
not going to fight with people to get my "suggestions" into the manual
against their explicitly expressed will (or lack thereof).


  reply	other threads:[~2010-09-22 19:36 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-23 20:13 Tom Tromey
2010-08-30 18:01 ` Tom Tromey
2010-08-30 18:24   ` Eli Zaretskii
2010-08-30 20:24     ` Tom Tromey
2010-08-30 20:43       ` Eli Zaretskii
2010-09-01 23:01         ` Tom Tromey
2010-09-02 10:32           ` Eli Zaretskii
2010-09-02 15:48             ` Tom Tromey
2010-09-02 18:40               ` Eli Zaretskii
2010-09-07 21:01                 ` Tom Tromey
2010-09-22 16:33                   ` Eli Zaretskii
2010-09-22 18:47                     ` Tom Tromey
2010-09-22 19:15                       ` Eli Zaretskii
2010-09-22 19:17                         ` Joel Brobecker
2010-09-22 19:19                           ` Eli Zaretskii
2010-09-22 19:26                             ` Tom Tromey
2010-09-22 19:59                               ` Eli Zaretskii [this message]
2010-09-22 20:57                                 ` Tom Tromey
2010-09-23 12:42                                   ` 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=83vd5xvaep.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@redhat.com \
    /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