From: Tom Tromey <tromey@redhat.com>
To: Paul Koning <Paul_Koning@dell.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PING] [RFC] Thread debug support for NetBSD 5
Date: Thu, 10 Jun 2010 17:30:00 -0000 [thread overview]
Message-ID: <m3eigeaj7b.fsf@fleche.redhat.com> (raw)
In-Reply-To: <19423.13061.223005.318137@pkoning-laptop.equallogic.com> (Paul Koning's message of "Mon, 3 May 2010 16:33:09 -0400")
>>>>> "Paul" == Paul Koning <Paul_Koning@dell.com> writes:
Paul> Excerpt of message (sent 29 April 2010) by Paul Koning:
Paul> Thanks for the review comments, attached is an updated patch.
I didn't see a response to this yet.
I am not really the best person to review it :-(.
However, I don't like patches to languish this long -- if you don't hear
a response in the next couple of weeks, please ping me and I will take a
stab at it.
Paul> Is the correct procedure for changes to configure.ac to regenerate
Paul> configure and include the resulting configure in the patch diffs also?
For gcc, the usual custom is to exclude generated files from the patch.
I am not sure whether this holds for gdb or not. I does not matter to
me personally, I just skip over the noisy bits.
Tom
next prev parent reply other threads:[~2010-06-10 17:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-20 15:49 Paul Koning
2010-04-22 15:36 ` Paul Koning
2010-04-29 14:49 ` [PING] " Paul Koning
2010-04-29 15:39 ` Pedro Alves
2010-05-03 13:51 ` Paul Koning
2010-04-30 12:44 ` Nick Hudson
2010-05-02 13:29 ` Mark Kettenis
2010-05-03 0:58 ` Paul Koning
2010-05-03 10:50 ` Paul Koning
2010-05-03 11:58 ` Mark Kettenis
2010-05-03 13:39 ` Paul Koning
2010-05-03 20:33 ` Paul Koning
2010-06-10 17:30 ` Tom Tromey [this message]
2010-06-11 14:02 ` Pedro Alves
2010-06-11 14:40 ` Paul Koning
2010-06-22 17:37 ` Mark Kettenis
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=m3eigeaj7b.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=Paul_Koning@dell.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