Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [cancel] [patch] More suggestive error_is_running message
Date: Tue, 17 Apr 2012 23:01:00 -0000	[thread overview]
Message-ID: <20120417225900.GP2852@adacore.com> (raw)
In-Reply-To: <20120417212234.GA21359@host2.jankratochvil.net>

> In general GDB should always suggest possible solutions to a problem.
> Stating just the problem may not be enough for the user.

Agreed on that. I have learnt to appreciate git's helpful hints
when something happens. We just need to find the right wording
to avoid being too verbose and undoing some of the benefits of
the work done earlier to cut on verbosity.  I realize it is
a little disingenous of me to put everything on the same level,
as some of the verbose output that was removed was simply useless
or redundant, but I didn't know how to express it concisely.

Anyway, what I was also trying to say is that my comments where
meant to try to help with the wording. More often than not,
I'll settle for something that works, or is good enough, even
if it's not perfect. We both use English as a second language,
so it's normal that we're having a tougher time writing good
English error messages.

-- 
Joel


      reply	other threads:[~2012-04-17 22:59 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
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 [this message]

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=20120417225900.GP2852@adacore.com \
    --to=brobecker@adacore.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