public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mec dot gnu at mindspring dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/14893] [3.5 Regression] 3.4.0-20040406, 'make install' fails on doc/gcjh.1
Date: Sun, 06 Jun 2004 04:08:00 -0000	[thread overview]
Message-ID: <20040606040814.25454.qmail@sourceware.org> (raw)
In-Reply-To: <20040408175851.14893.mec.gnu@mindspring.com>


------- Additional Comments From mec dot gnu at mindspring dot com  2004-06-06 04:08 -------
Subject: Re:  [3.5 Regression] 3.4.0-20040406, 'make install' fails on doc/gcjh.1

Hi Giovanni and Alexandre,

Thanks for catching this, it looks like something obvious fell through
the cracks.  It is needed for 3.5.0.

The status of this patch is: Alexandre said "this is ok for mainline"
but then he asked for a small portability tweak.  I did the tweak and
re-tested the patch and re-submitted the patch here:

  http://gcc.gnu.org/ml/gcc-patches/2004-04/msg01529.html

But then I didn't hear back from Alexandre.

Maybe Alexandre meant "yeah, this is okay after you make that small
fix, I trust you know what you are doing", and I was too pedantic
asking for another approval?  Anyways, not trying to point any fingers,
just trying to clean up the loose edge.

Alexandre, can you review this PR (14893), and then look at my
silly little patch again, and say whether it's okay?

Thanks,

Michael C


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14893


  parent reply	other threads:[~2004-06-06  4:08 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-08 17:58 [Bug bootstrap/14893] New: " mec dot gnu at mindspring dot com
2004-04-08 18:00 ` [Bug bootstrap/14893] " mec dot gnu at mindspring dot com
2004-04-08 18:02 ` [Bug bootstrap/14893] [3.4 Regression] " pinskia at gcc dot gnu dot org
2004-04-08 18:06 ` mec dot gnu at mindspring dot com
2004-04-08 18:07 ` mec dot gnu at mindspring dot com
2004-04-08 18:07 ` mec dot gnu at mindspring dot com
2004-04-08 19:58 ` prj-bugzilla-gcc at multivac dot cwru dot edu
2004-04-09 18:18 ` mec dot gnu at mindspring dot com
2004-04-09 18:32 ` prj at po dot cwru dot edu
2004-04-09 19:46 ` mec dot gnu at mindspring dot com
2004-04-10  2:59 ` mec dot gnu at mindspring dot com
2004-04-10  3:04 ` prj at po dot cwru dot edu
2004-04-11 20:20 ` mmitchel at gcc dot gnu dot org
2004-04-11 22:17 ` mec dot gnu at mindspring dot com
2004-04-12  8:05 ` prj at po dot cwru dot edu
2004-04-12 12:51 ` aoliva at gcc dot gnu dot org
2004-04-12 16:03 ` prj-bugzilla-gcc at multivac dot cwru dot edu
2004-04-13  4:21 ` aoliva at gcc dot gnu dot org
2004-04-13 20:11 ` mec dot gnu at mindspring dot com
2004-04-14 10:10 ` mmitchel at gcc dot gnu dot org
2004-04-14 21:14 ` cvs-commit at gcc dot gnu dot org
2004-04-14 23:20 ` [Bug bootstrap/14893] [3.5 " pinskia at gcc dot gnu dot org
2004-04-15  7:03 ` aoliva at gcc dot gnu dot org
2004-06-06  3:53 ` giovannibajo at libero dot it
2004-06-06  4:08 ` mec dot gnu at mindspring dot com [this message]
2004-08-03 22:56 ` aoliva at gcc dot gnu dot org
2004-08-05 19:29 ` cvs-commit at gcc dot gnu dot org
2004-08-05 19:35 ` pinskia at gcc dot gnu dot org

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=20040606040814.25454.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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. 
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).