From: Joel Brobecker <brobecker@adacore.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Ping: unconditionally print detaching message
Date: Fri, 19 Nov 2010 22:16:00 -0000 [thread overview]
Message-ID: <20101119221615.GK2634@adacore.com> (raw)
In-Reply-To: <m3bp5l9dtl.fsf@fleche.redhat.com>
> While going through the Fedora patch backlog I ran into this:
>
> http://sources.redhat.com/ml/gdb-patches/2007-12/msg00087.html
>
> This has just one reply, from Daniel, asking Jan to see what the other
> maintainers think.
FWIW:
I don't really have an opinion either way. Some people are going
to find it annoying if they are too many forks going on (unlikely?),
while some others might have their life saved by it (but that's
provided we keep the number of warnings small).
> It occurred to me that perhaps we could instead have a setting for this.
> I am ambivalent about that but if that is what people want, I will
> implement it.
We could introduce message without a setting for now - the fewer,
the better (IMO). And if people complain about it, then introduce
one to prevent from being printed if the user so wishes...
--
Joel
next prev parent reply other threads:[~2010-11-19 22:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-19 21:57 Tom Tromey
2010-11-19 22:16 ` Joel Brobecker [this message]
2010-12-06 21:56 ` Tom Tromey
2010-12-07 7:56 ` Jan Kratochvil
2010-12-07 18:14 ` Tom Tromey
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=20101119221615.GK2634@adacore.com \
--to=brobecker@adacore.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