From: Eli Zaretskii <eliz@gnu.org>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: --with-pkgversion and --with-bugurl support for GDB
Date: Tue, 20 May 2008 00:05:00 -0000 [thread overview]
Message-ID: <ufxsei0tu.fsf@gnu.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0805191702570.19513@digraph.polyomino.org.uk>
> Date: Mon, 19 May 2008 17:06:55 +0000 (UTC)
> From: "Joseph S. Myers" <joseph@codesourcery.com>
>
> * gdb.texinfo: Use VERSION_PACKAGE and BUGURL. Remove
> mailing-list-specific text about bug reporting.
Thanks. This part of the patch is approved, except...
> +@ifset BUGURL
> In any event, we also recommend that you submit bug reports for
> -@value{GDBN}. The preferred method is to submit them directly using
> -@uref{http://www.gnu.org/software/gdb/bugs/, @value{GDBN}'s Bugs web
> -page}. Alternatively, the @email{bug-gdb@@gnu.org, e-mail gateway} can
> -be used.
> -
> -@strong{Do not send bug reports to @samp{info-gdb}, or to
> -@samp{help-gdb}, or to any newsgroups.} Most users of @value{GDBN} do
> -not want to receive bug reports. Those that do have arranged to receive
> -@samp{bug-gdb}.
> -
> -The mailing list @samp{bug-gdb} has a newsgroup @samp{gnu.gdb.bug} which
> -serves as a repeater. The mailing list and the newsgroup carry exactly
> -the same messages. Often people think of posting bug reports to the
> -newsgroup instead of mailing them. This appears to work, but it has one
> -problem which can be crucial: a newsgroup posting often lacks a mail
> -path back to the sender. Thus, if we need to ask for more information,
> -we may be unable to reach you. For this reason, it is better to send
> -bug reports to the mailing list.
> +@value{GDBN} to @value{BUGURL}.
> +@end ifset
Why do you want to remove all this stuff? If you don't want it under
BUGURL/VERSION_PACKAGE (whose utility, I must admit, I don't fully
understand), then please leave it alone when BUGURL is NOT set. If
you _really_ think it's a good idea to remove this text
unconditionally, please at least tell why you think so.
next prev parent reply other threads:[~2008-05-19 18:52 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 [this message]
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
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=ufxsei0tu.fsf@gnu.org \
--to=eliz@gnu.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