public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tom@tromey.com>
Subject: Re: [PATCH v2] [gdb/cli] Fix wrapping for TERM=ansi
Date: Fri, 5 May 2023 15:27:45 +0200	[thread overview]
Message-ID: <a62c261c-941f-dc09-3f06-708b249b88dd@suse.de> (raw)
In-Reply-To: <20230502133258.8380-1-tdevries@suse.de>

I've submitted a v3.

Changes since v2:
- testsuite part is now just removing KFAILs
- I've dropped the bit about "set width" semantics.  I still think it's
   worthwhile, but I think I should sent it as a separate patch
   (and I'm thinking about adding a warning when setting width to
   something different than 0 or the auto-detected width).

I'm fairly happy with the v3, and intend to commit end of next week, 
unless there are comments.

Thanks,
- Tom


  reply	other threads:[~2023-05-05 13:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-02 13:32 Tom de Vries
2023-05-05 13:27 ` Tom de Vries [this message]
2023-05-12  9:45   ` Tom de Vries

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=a62c261c-941f-dc09-3f06-708b249b88dd@suse.de \
    --to=tdevries@suse.de \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.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).