From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Code cleanup: bpstat_alloc calling semantics standardization
Date: Tue, 24 Aug 2010 21:33:00 -0000 [thread overview]
Message-ID: <m3r5hnn1as.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20100819081638.GA4171@host1.dyn.jankratochvil.net> (Jan Kratochvil's message of "Thu, 19 Aug 2010 10:16:38 +0200")
>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
Tom> Just to be clear, I assume this is obsoleted by Pedro's other fix for PR
Tom> 11371.
Jan> It is no longer a prerequisite for the PR 11371 fix.
Jan> Still it is a valid code cleanup. Which is not much of worth.
Once you have written a cleanup, it might as well go in.
Jan> Updated the patch.
I think it looks good, but I would prefer that Pedro say yes or no.
Tom
next prev parent reply other threads:[~2010-08-24 21:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-11 20:11 Jan Kratochvil
2010-08-18 22:48 ` Tom Tromey
2010-08-19 8:16 ` Jan Kratochvil
2010-08-24 21:33 ` Tom Tromey [this message]
2010-08-24 22:09 ` Pedro Alves
2010-08-30 9:49 ` Jan Kratochvil
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=m3r5hnn1as.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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).