From: Vasili Burdo <vasili.burdo@gmail.com>
To: Vasili Burdo via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] [PING #2] TUI disassembly window improvement, take 2
Date: Fri, 2 Jul 2021 14:43:23 +0300 [thread overview]
Message-ID: <CANacp61cqwWEzDLZR7eL=_OFPGv=EwxzJfToVutc5cSQ6qxJeg@mail.gmail.com> (raw)
In-Reply-To: <CANacp60gpfB8o1JLnp7CTX8vKzxQUMDA1K29qGnfjF11E+q9Uw@mail.gmail.com>
Ping!
2 packets transmitted, 0 received, 100% packet loss, time 3 weeks
Thanks.
Vasili
пн, 28 июн. 2021 г. в 17:45, Vasili Burdo <vasili.burdo@gmail.com>:
>
> Ping!
>
> вт, 22 июн. 2021 г. в 16:56, Vasili Burdo <vasili.burdo@gmail.com>:
> >
> > Hi,
> >
> > I've got GDB copyright assignment RT:1731775, so, I'm resending my
> > patch - see attachment.
> >
> > Previous discussion thread and exlanation what's changed is here:
> > https://sourceware.org/pipermail/gdb-patches/2021-June/179693.html and
> > here: https://sourceware.org/pipermail/gdb-patches/2021-June/179695.html
> >
> > Changes in current patch:
> > - Added changelog entry
> > - Tom Tromey's comments are addressed.
> > - Disasm window title is kept intact. Reason - everything important is
> > already displayed in status line, so, no useful information for title
> > remains.
> >
> > Thanks.
> > Vasili
next prev parent reply other threads:[~2021-07-02 11:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 13:56 [PATCH] " Vasili Burdo
2021-06-28 14:45 ` [PATCH] [PING] " Vasili Burdo
2021-07-02 11:43 ` Vasili Burdo [this message]
2021-07-06 11:18 ` [PATCH] [PING #3] " Vasili Burdo
2021-07-12 20:51 ` [PING][#4][PATCH] " Vasili Burdo
2021-07-16 11:25 ` [PING][#5][PATCH] " Vasili Burdo
2021-07-28 10:57 ` Vasili Burdo
2021-08-05 10:46 ` [PING][#6][PATCH] " Vasili Burdo
2021-08-05 14:40 ` Simon Marchi
2022-01-23 19:53 ` [PATCH] " Simon Marchi
2022-01-23 20:03 ` Simon Marchi
2022-01-24 14:51 ` Simon Marchi
2022-01-24 16:07 ` Vasili Burdo
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='CANacp61cqwWEzDLZR7eL=_OFPGv=EwxzJfToVutc5cSQ6qxJeg@mail.gmail.com' \
--to=vasili.burdo@gmail.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).