Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Make file-based lookup more interruptable
Date: Tue, 02 Jun 2015 00:03:00 -0000	[thread overview]
Message-ID: <CADPb22Q6b6MF2yNqg43=LgReroiZ-qivGsrSmiUJxsPAPx6fEg@mail.gmail.com> (raw)
In-Reply-To: <CADPb22TDaetTJyuTHPJboyziJAzoP88N7Gii6iOYfTmPXsNCLg@mail.gmail.com>

On Fri, May 22, 2015 at 10:46 AM, Doug Evans <dje@google.com> wrote:
> On Tue, May 19, 2015 at 4:55 AM, Yao Qi <qiyaoltc@gmail.com> wrote:
>> Doug Evans <dje@google.com> writes:
>>
>>> This patch makes, for example, "b 'foo.c':bar" more interruptable.
>>
>> Does 'interruptable' mean user can type ctrl-c to cancel the command
>> "b 'foo.c':bar" which may take 10 minutes?  If so, this change is
>> visible to users, and do we need to add a NEWS entry?
>
> I'd classify this as being no different than a performance improvement.
> There already is a level of interruptability, the only change is in degree
> of responsiveness.
>
> We *can* start adding such things to NEWS, but we don't do so today.
> Before we start imposing this on everyone, we'll need to establish
> what does and does not qualify - I'm guessing we don't want to add
> a NEWS entry for every little performance improvement.

Hi.

"ping" :-)

Whaddayathink? Should we start adding perf improvements to NEWS
(and try to classify what is newsworthy)?
Or let it go, at least for now?


  reply	other threads:[~2015-06-02  0:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-15 22:20 Doug Evans
2015-05-19 11:55 ` Yao Qi
2015-05-22 17:46   ` Doug Evans
2015-06-02  0:03     ` Doug Evans [this message]
2015-06-02  7:59     ` Yao Qi
2015-06-02 12:34       ` Doug Evans
2015-06-02 13:08         ` Yao Qi
2015-06-02 13:20           ` Doug Evans
2015-06-02 13:46             ` Yao Qi

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='CADPb22Q6b6MF2yNqg43=LgReroiZ-qivGsrSmiUJxsPAPx6fEg@mail.gmail.com' \
    --to=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=qiyaoltc@gmail.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