From: Ishikawa <ishikawa@yk.rim.or.jp>
Cc: emacs-pretesters@gnu.org, emacs-devel@gnu.org,
eggert@twinsun.com, ebotcazou@gcc.gnu.org,
gcc-patches@gcc.gnu.org
Subject: Re: (RFC) GCC minor document change: gcc.1
Date: Tue, 15 Jul 2003 14:46:56 +0900 [thread overview]
Message-ID: <3F139550.2E8811FC@yk.rim.or.jp> (raw)
In-Reply-To: 3F1385EB.2090300@tuliptree.org
Jim Wilson wrote:
>
> Ishikawa wrote:
> > The file that should be patched is invoke.texi.
>
> I don't think this helps much. Someone reading the documentation for
> the -fno-zero-initialized-in-bss option to learn what it does isn't
> helped by the fact that it affects GNU Emacs. Someone reading the
> documentation to figure out why GNU Emacs doesn't work isn't going to
> know that they are supposed to look at the documentation for this option.
I agree that this is not among the first files, someone
with the problem is going to read.
> I suggest putting the info someplace else, such as in the 3.3 release notes.
> http://gcc.gnu.org/gcc-3.3/changes.html
> Or maybe on the known bugs page.
> http://gcc.gnu.org/bugs.html#known
I think the former may be good enough.
Now I am wondering if the message is reaching people who has
the authority to modify the changes.html.
--
int main(void){int j=2003;/*(c)2003 cishikawa. */
char t[] ="<CI> @abcdefghijklmnopqrstuvwxyz.,\n\"";
char *i ="g>qtCIuqivb,gCwe\np@.ietCIuqi\"tqkvv is>dnamz";
while(*i)((j+=strchr(t,*i++)-(int)t),(j%=sizeof t-1),
(putchar(t[j])));return 0;}/* under GPL */
next prev parent reply other threads:[~2003-07-15 5:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-14 23:52 (RFC) GCC minor document change: gcc.1 ishikawa
2003-07-14 23:55 ` Andrew Pinski
2003-07-15 0:03 ` Ishikawa
2003-07-15 4:41 ` Jim Wilson
2003-07-15 5:46 ` Ishikawa [this message]
2003-07-15 7:34 ` Paul Eggert
2003-07-15 16:23 ` Ishikawa
2003-07-15 23:46 ` Ishikawa
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3F139550.2E8811FC@yk.rim.or.jp \
--to=ishikawa@yk.rim.or.jp \
--cc=ebotcazou@gcc.gnu.org \
--cc=eggert@twinsun.com \
--cc=emacs-devel@gnu.org \
--cc=emacs-pretesters@gnu.org \
--cc=gcc-patches@gcc.gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).