Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: ac131313@cygnus.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [5.2:rfa/doc] Mention http://www.gnu.org/software/gdb/bugs/
Date: Thu, 28 Mar 2002 23:23:00 -0000	[thread overview]
Message-ID: <9003-Fri29Mar2002101915+0300-eliz@is.elta.co.il> (raw)
In-Reply-To: <3CA3C6ED.9060506@cygnus.com> (message from Andrew Cagney on Thu, 28 Mar 2002 20:44:13 -0500)

> Date: Thu, 28 Mar 2002 20:44:13 -0500
> From: Andrew Cagney <ac131313@cygnus.com>
>  
> -   For more information on how/whether to report bugs, see the GDB
> -Bugs section of the GDB manual (gdb/doc/gdb.texinfo) or the
> -gdb/CONTRIBUTE file.
> +   For more information on how/whether to report bugs, see the
> +Reporting Bugs chapter of the GDB manual (gdb/doc/gdb.texinfo.

A closing paren is missing from the last line.

> -In any event, we also recommend that you send bug reports for
> -@value{GDBN} to this addresses:
> +In any event, we also recommend that you submit bug reports for
> +@value{GDBN}.  The prefered method is to submit them directly using the
> +World Wide Web, see:
>  
>  @example
> -bug-gdb@@gnu.org
> +@uref{http://www.gnu.org/software/gdb/bugs/}
>  @end example

This looks awkward in HTML, I think.  Since @uref actually produces
a link in all formats that support links, I suggest to rewrite like
this:

  In any even, we also recommend that you submit bug reports for
  @value{GDBN}.  The prefered method is to submit them directly using
  the @uref{http://www.gnu.org/software/gdb/bugs/, World Wide Web}.

> +@noindent
> +Alternatively, the e-mail address @email{bug-gdb@@gnu.org} can be used.

Same here:

   Alternately, the @email{bug-gdb@@gnu.org, e-mail gateway} can be
   used.


  reply	other threads:[~2002-03-29  7:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-28 15:20 Andrew Cagney
2002-03-28 17:46 ` Andrew Cagney
2002-03-28 23:23   ` Eli Zaretskii [this message]
2002-04-07 12:06     ` Andrew Cagney

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=9003-Fri29Mar2002101915+0300-eliz@is.elta.co.il \
    --to=eliz@is.elta.co.il \
    --cc=ac131313@cygnus.com \
    --cc=gdb-patches@sources.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