Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: drow@false.org, gdb-patches@sourceware.org
Subject: Re: --with-pkgversion and --with-bugurl support for GDB
Date: Fri, 06 Jun 2008 10:21:00 -0000	[thread overview]
Message-ID: <ufxrqc1cb.fsf@gnu.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0806052127230.9469@digraph.polyomino.org.uk>

> Date: Thu, 5 Jun 2008 21:28:15 +0000 (UTC)
> From: "Joseph S. Myers" <joseph@codesourcery.com>
> cc: gdb-patches@sourceware.org
> 
> +static void
> +gdbreplay_version (void)
> +{
> +  printf ("GNU gdbreplay %s%s\n"
> +	  "Copyright (C) 2008 Free Software Foundation, Inc.\n"
> +	  "gdbserver is free software, covered by the GNU General Public License.\n"
> +	  "This gdbserver was configured as \"%s\"\n",
> +	  PKGVERSION, version, host_name);

We start by announcing a "GNU gdbreplay", but thereafter talk about
"gdbserver".  Is that right?  Shouldn't we either (1) use gdbreplay
throughout, or (2) say something like "GNU gdbreplay (gdbserver %s%s)"?


  parent reply	other threads:[~2008-06-06 10:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-19 20:46 Joseph S. Myers
2008-05-20  0:05 ` Eli Zaretskii
2008-05-20  3:26   ` Joseph S. Myers
2008-05-20 15:25     ` Eli Zaretskii
2008-05-20 18:24       ` Joseph S. Myers
2008-05-21  2:54         ` Eli Zaretskii
2008-05-30 15:23         ` Ping " Joseph S. Myers
2008-06-05 20:24         ` Daniel Jacobowitz
2008-06-05 21:28           ` Joseph S. Myers
2008-06-05 21:45             ` Daniel Jacobowitz
2008-06-06 10:21             ` Eli Zaretskii [this message]
2008-06-06 20:22               ` Joseph S. Myers
2008-06-06 20:26                 ` Daniel Jacobowitz
2008-06-06 20:32                 ` Eli Zaretskii
2008-06-10 12:58             ` Andreas Schwab

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=ufxrqc1cb.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=joseph@codesourcery.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