From: "Metzger, Markus T" <markus.t.metzger@intel.com>
To: Alex Chronopoulos <achronop@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [PATCH v2] Change message when reaching end of reverse history.
Date: Fri, 12 Apr 2024 05:39:38 +0000 [thread overview]
Message-ID: <DM8PR11MB5749A67AB43014A4D47941A2DE042@DM8PR11MB5749.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CAN7Yog4UqKxDBahmm5DKwxCWEBZ2mxLCNgnM=3zDZ7d2HdCjHA@mail.gmail.com>
>> This line got too long.
>
>All these are *.exp files and I cannot find an easy way to reduce the line length without breaking the expectations test. On the other hand, I see more *.exp files with much longer lines. Do you know how to make the line shorter in his case?
The test doesn't need to cover the full text. It needs just enough to confirm
that we ran out of history.
When matching the prompt at the end, you can use -wrap before the string
and omit '$gdb_prompt $' at the end.
Regards,
Markus.
Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de <http://www.intel.de>
Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next prev parent reply other threads:[~2024-04-12 5:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-07 19:55 Alex Chronopoulos
2024-04-08 7:15 ` Metzger, Markus T
2024-04-11 16:46 ` Alex Chronopoulos
2024-04-12 5:39 ` Metzger, Markus T [this message]
2024-04-08 11:12 ` Eli Zaretskii
2024-04-09 18:05 ` Guinevere Larsen
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=DM8PR11MB5749A67AB43014A4D47941A2DE042@DM8PR11MB5749.namprd11.prod.outlook.com \
--to=markus.t.metzger@intel.com \
--cc=achronop@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).