From: Doug Evans <dje@google.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH, doc RFA] New option -B: simplify running gdb from build directory
Date: Fri, 07 Mar 2014 18:54:00 -0000 [thread overview]
Message-ID: <CADPb22Q6kyG7DVTzwgoJzBBgsJ8BZ9=-UCwyseTALZV=L4+__g@mail.gmail.com> (raw)
In-Reply-To: <83y50lq2b8.fsf@gnu.org>
On Fri, Mar 7, 2014 at 10:41 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Fri, 7 Mar 2014 09:37:28 -0800
>> From: Doug Evans <dje@google.com>
>> Cc: gdb-patches <gdb-patches@sourceware.org>
>>
>> On Thu, Mar 6, 2014 at 11:10 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>>
>> > > From: Doug Evans <dje@google.com>
>> > > Date: Thu, 6 Mar 2014 13:41:21 -0800
>> > >
>> > > I believe I've addressed Eli's comments,
>> > > [ref: https://sourceware.org/ml/gdb-patches/2013-12/msg00969.html]
>> >
>> > No, I don't think you have.
>>
>> That's not much to go on. :-)
>
> "Address the comments" in my book means to make changes to accommodate
> those comments. In contrast, what you did was express your
> disagreement with my comments. That doesn't seem to fit the bill.
Ah. Definition mismatch..
I'll try to remember to phrase "Address the comments" differently next time.
Thanks.
next prev parent reply other threads:[~2014-03-07 18:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-27 19:42 [RFC] " Doug Evans
2013-12-27 19:54 ` Doug Evans
2013-12-27 20:15 ` Eli Zaretskii
2013-12-27 20:51 ` Doug Evans
2014-03-06 21:41 ` [PATCH, doc RFA] " Doug Evans
2014-03-07 7:10 ` Eli Zaretskii
[not found] ` <CADPb22RKaBx1p2vF4-wGODZVe-QqdGc93Ax-bD82xb9Adr5EJw@mail.gmail.com>
2014-03-07 18:41 ` Eli Zaretskii
2014-03-07 18:54 ` Doug Evans [this message]
2014-03-25 1:02 ` Doug Evans
2014-03-25 1:20 ` Doug Evans
2014-03-25 1:28 ` Doug Evans
2014-04-28 22:35 ` [PATCH, doc RFA] New option -D: alias for --data-directory Doug Evans
2014-04-29 2:37 ` Eli Zaretskii
2014-05-16 19:17 ` Doug Evans
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='CADPb22Q6kyG7DVTzwgoJzBBgsJ8BZ9=-UCwyseTALZV=L4+__g@mail.gmail.com' \
--to=dje@google.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/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