public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Sterling Augustine <saugustine@google.com>
To: Peng Yu <pengyu.ut@gmail.com>
Cc: Christian Biesinger <cbiesinger@google.com>,
	Reuben Thomas via Gdb <gdb@sourceware.org>
Subject: Re: How to display instructions around the current instuction?
Date: Thu, 28 Jan 2021 18:47:11 -0800	[thread overview]
Message-ID: <CAEG7qUySk07zeuByVCuk6HpAsfGiizVCvQ6MAuwQPTkKt0J3jA@mail.gmail.com> (raw)
In-Reply-To: <CABrM6wkyHcYJe2kJv3PXjO5ZPjz+1WvvPPOq9dNQDr3Fxm89jg@mail.gmail.com>

On Thu, Jan 28, 2021 at 6:33 PM Peng Yu <pengyu.ut@gmail.com> wrote:
> > You have a strange, rather binary view, of "correct" vs "incorrect".
> > Every single idea here does something approximately like what you
> > want. Many people in the past asking similar questions would have been
> > perfectly fine with a wide variety of answers. You might not like it,
> > but you don't get to decide what the proper etiquette in this mailing
> > list.
>
> So, you get to decide it?

The community gets to decide it. Not you. The community responded in
the typical way it has for years. If that is unacceptable to you, then
you don't seem to be a part of the community.
> > How many patches do have in gdb again?
>
> I don't see this is a relevant question here. If you want to ask that
> question, go to gdb-patches.

The relevance is that you have not been a part of the community in the
past, but you expect it to work in a very particular way, and it has
never worked that way. Why should it change now, just for you? Someone
who has never contributed in any way to the community?

You seem to be confusing Peng's problem with "other people's problem".
You came to the mailing list with a problem. That was Peng's problem.
We would like to help you with your problem, but whether we can or
can't doesn't make it our problem.

Someone gives you an answer that doesn't solve your problem? That's
your problem, not the answerer's problem. Your problem is not our
problem. How we answer doesn't make it our problem.

  reply	other threads:[~2021-01-29  2:47 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-27 23:12 Peng Yu
2021-01-28  8:48 ` Andreas Schwab
2021-01-28 17:08   ` Peng Yu
2021-01-28 18:44     ` Andreas Schwab
2021-01-29 17:38       ` Tavis Ormandy
2021-01-28  9:19 ` Stefan Puiu
2021-01-28 17:06   ` Peng Yu
2021-01-28 17:26     ` Eli Zaretskii
2021-01-28 17:37       ` Peng Yu
2021-01-28 17:41         ` Christian Biesinger
2021-01-29  2:07           ` Peng Yu
2021-01-29  2:22             ` Sterling Augustine
2021-01-29  2:32               ` Peng Yu
2021-01-29  2:47                 ` Sterling Augustine [this message]
2021-01-28 17:57         ` Eli Zaretskii
2021-01-28 18:00     ` Stefan Puiu
2021-01-29  2:15       ` Peng Yu
2021-01-28 13:11 ` Christian Biesinger
2021-01-28 16:50   ` Peng Yu
2021-01-28 16:53     ` Christian Biesinger
2021-01-28 17:16       ` Peng Yu
2021-01-28 17:16         ` Christian Biesinger
2021-01-28 17:00     ` Sterling Augustine
     [not found]       ` <CAGOmfbFh+6AJZFsDP8nFH1bs6kntC4khO+YmPkn3LUfcLAspZw@mail.gmail.com>
2021-01-28 17:45         ` Peng Yu
2021-01-28 18:27 ` Pedro Alves
2021-01-29  1:58   ` Peng Yu
2021-01-29  7:18     ` 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=CAEG7qUySk07zeuByVCuk6HpAsfGiizVCvQ6MAuwQPTkKt0J3jA@mail.gmail.com \
    --to=saugustine@google.com \
    --cc=cbiesinger@google.com \
    --cc=gdb@sourceware.org \
    --cc=pengyu.ut@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).