From: Tom Tromey <tromey@redhat.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [patch] More suggestive error_is_running message
Date: Thu, 12 Apr 2012 15:28:00 -0000 [thread overview]
Message-ID: <87lim10yhg.fsf@fleche.redhat.com> (raw)
In-Reply-To: <m3sjgb1098.fsf@redhat.com> (Sergio Durigan Junior's message of "Tue, 10 Apr 2012 23:16:19 -0300")
Sergio> In such cases I never know if those new standards apply for new
Sergio> projects, or for existing projects as well. If they apply to existing
Sergio> projects, then I'm not sure there should be any massive
Sergio> replacement/adjustment in the codebase to reflect those new rules.
I tend to think we should change, but it is a surprisingly tricky area.
Tom
next prev parent reply other threads:[~2012-04-12 15:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-10 19:20 Jan Kratochvil
2012-04-10 21:30 ` Sergio Durigan Junior
2012-04-11 2:16 ` Jan Kratochvil
2012-04-11 4:55 ` Sergio Durigan Junior
2012-04-12 15:28 ` Tom Tromey [this message]
2012-04-11 15:35 ` Joel Brobecker
2012-04-11 15:48 ` [cancel] " Jan Kratochvil
2012-04-11 17:17 ` Joel Brobecker
2012-04-17 21:26 ` Jan Kratochvil
2012-04-17 23:01 ` Joel Brobecker
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=87lim10yhg.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=sergiodj@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