public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Patrick Palka <patrick@parcs.ath.cx>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Add option to remove duplicate command history entries
Date: Fri, 26 Jun 2015 14:50:00 -0000	[thread overview]
Message-ID: <558D66A3.9010305@redhat.com> (raw)
In-Reply-To: <CA+C-WL9M-qdL+_CkPPr6edmwxubcPKUve+k_XykYKex7-txOsQ@mail.gmail.com>

On 06/26/2015 03:30 PM, Patrick Palka wrote:

>>> +    gdb_test "print 0"
>>> +    gdb_test "print 1"
>>> +    gdb_test "print 2"
>>> +    gdb_test "print 1"
>>> +    gdb_test "print 1"
>>> +    gdb_test "print 2"
>>> +    gdb_test "print 3"
>>> +    gdb_test "print 3"
>>> +    gdb_test "print 4"
>>> +    gdb_test "print 1"
>>> +    gdb_test "print 2"
>>> +    gdb_test "print 3"
>>> +    gdb_test "print 4"
>>
>> Duplicate test names here.  This should catch all:
> 
> I could use some kind of loop over a list here I think, prefixing each
> test name with the index of the list.

Yeah, that would be fine.

Thanks,
Pedro Alves

  reply	other threads:[~2015-06-26 14:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-04 16:22 Patrick Palka
2015-06-04 16:47 ` Eli Zaretskii
2015-06-04 18:54   ` Patrick Palka
2015-06-04 19:25     ` Eli Zaretskii
2015-06-09 18:10 ` Pedro Alves
2015-06-09 18:41   ` Patrick Palka
2015-06-10 15:12     ` Pedro Alves
2015-06-19 23:33       ` Patrick Palka
2015-06-20  6:52         ` Eli Zaretskii
2015-06-26 13:35         ` Patrick Palka
2015-06-26 14:18         ` Pedro Alves
2015-06-26 14:30           ` Patrick Palka
2015-06-26 14:50             ` Pedro Alves [this message]
2015-06-26 15:12         ` Patrick Palka

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=558D66A3.9010305@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=patrick@parcs.ath.cx \
    /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).