From: Doug Evans <dje@google.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [0/4] RFC: add DWARF index support
Date: Tue, 10 Aug 2010 18:57:00 -0000 [thread overview]
Message-ID: <AANLkTiku_sfPq75Cb27ZD2tjZr-HxDvG+hCcRwWRE56a@mail.gmail.com> (raw)
In-Reply-To: <m3hbj2cnlv.fsf@fleche.redhat.com>
On Tue, Aug 10, 2010 at 11:46 AM, Tom Tromey <tromey@redhat.com> wrote:
>>>>>> "Doug" == Doug Evans <dje@google.com> writes:
>
> Doug> Are you sure you'll just ignore *all* such errors?
>
> Yes.
>
> Doug> I suspect you'd want to at least catch, for example, spelling errors
> Doug> in file names passed to the script.
>
> There won't be spelling errors, since in our use gdb-add-index is run
> from an RPM build script.
And RPM build scripts never have bugs, including while they're being developed?
But ok, it's not that important.
next prev parent reply other threads:[~2010-08-10 18:57 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-30 22:33 Tom Tromey
2010-07-09 17:31 ` Tom Tromey
2010-07-09 17:45 ` Eli Zaretskii
2010-07-09 20:26 ` Tom Tromey
2010-07-10 7:03 ` Eli Zaretskii
2010-07-12 16:52 ` Tom Tromey
2010-07-22 11:31 ` Jan Kratochvil
2010-07-22 15:54 ` Tom Tromey
2010-07-30 20:46 ` Tom Tromey
2010-08-02 18:10 ` Doug Evans
2010-08-05 16:30 ` Tom Tromey
2010-08-05 16:32 ` Doug Evans
2010-08-05 19:55 ` Tom Tromey
2010-08-05 19:57 ` Tom Tromey
2010-08-06 17:15 ` Doug Evans
2010-08-06 17:40 ` Tom Tromey
2010-08-06 20:53 ` Doug Evans
2010-08-09 20:36 ` Tom Tromey
2010-08-09 21:16 ` Doug Evans
2010-08-10 18:46 ` Tom Tromey
2010-08-10 18:57 ` Doug Evans [this message]
2010-08-09 20:25 ` Jan Kratochvil
2010-08-09 20:43 ` Tom Tromey
2010-08-09 20:33 ` Jan Kratochvil
2010-07-13 20:42 ` Tom Tromey
2010-07-22 4:28 ` Paul Pluzhnikov
2010-07-22 14:14 ` Tom Tromey
2010-07-22 15:54 ` Tom Tromey
2010-07-22 16:20 ` Paul Pluzhnikov
2010-07-22 20:54 ` Tom Tromey
2010-07-23 22:12 ` Tom Tromey
2010-07-26 18:41 ` Ken Werner
2010-07-26 18:50 ` Tom Tromey
2010-07-27 7:58 ` Ken Werner
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=AANLkTiku_sfPq75Cb27ZD2tjZr-HxDvG+hCcRwWRE56a@mail.gmail.com \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.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).