From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>
Subject: Re: [patch 1/2] Code cleanup: infcall fields moving
Date: Fri, 26 Nov 2010 10:36:00 -0000 [thread overview]
Message-ID: <201011261036.01155.pedro@codesourcery.com> (raw)
In-Reply-To: <20101126044447.GA25724@host0.dyn.jankratochvil.net>
On Friday 26 November 2010 04:44:47, Jan Kratochvil wrote:
> > and then making struct thread_info embed a field of those,
> > instead of all the the field duplication.
>
> OK, done, I thought it will be too invasive but maybe it is OK.
I was only suggesting it for a rainy day. :-)
> Do you agree with this approach/naming?
I do. I like this. Thanks much for doing it!
--
Pedro Alves
next prev parent reply other threads:[~2010-11-26 10:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-24 0:51 [patch 3/3] Fix stale tp->step_resume_breakpoint Jan Kratochvil
2010-11-24 12:43 ` Pedro Alves
2010-11-26 4:46 ` [patch 1/2] Code cleanup: infcall fields moving Jan Kratochvil
2010-11-26 10:36 ` Pedro Alves [this message]
2010-11-28 4:34 ` Jan Kratochvil
2010-11-26 4:48 ` [patch 2/2] Fix stale tp->step_resume_breakpoint Jan Kratochvil
2010-11-28 4:35 ` 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=201011261036.01155.pedro@codesourcery.com \
--to=pedro@codesourcery.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