public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rwild at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/15479] Ada manual problems
Date: Sun, 24 Feb 2008 22:39:00 -0000	[thread overview]
Message-ID: <20080224223836.3027.qmail@sourceware.org> (raw)
In-Reply-To: <bug-15479-230@http.gcc.gnu.org/bugzilla/>



------- Comment #6 from rwild at gcc dot gnu dot org  2008-02-24 22:38 -------
Subject: Bug 15479

Author: rwild
Date: Sun Feb 24 22:37:52 2008
New Revision: 132601

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=132601
Log:
PR documentation/15479
* gnat_ugn.texi (Using gnatmake in a Makefile): Do not ignore errors
in Makefile rules, by using `&&' rather than `;'.

Modified:
    trunk/gcc/ada/ChangeLog
    trunk/gcc/ada/gnat_ugn.texi


-- 


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


  parent reply	other threads:[~2008-02-24 22:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-15479-230@http.gcc.gnu.org/bugzilla/>
2008-02-03 14:57 ` Ralf dot Wildenhues at gmx dot de
2008-02-17 21:21 ` rwild at gcc dot gnu dot org
2008-02-20 19:50 ` rwild at gcc dot gnu dot org
2008-02-20 19:52 ` rwild at gcc dot gnu dot org
2008-02-24 22:39 ` rwild at gcc dot gnu dot org [this message]
2008-02-24 22:41 ` rwild at gcc dot gnu dot org
2008-02-24 22:45 ` rwild at gcc dot gnu dot org
2008-03-02 22:38 ` rwild at gcc dot gnu dot org
2008-03-23 23:20 ` rwild at gcc dot gnu dot org
2008-05-12 23:12 ` charlet at gcc dot gnu dot org
2008-07-14 18:51 ` rwild at gcc dot gnu dot org
2008-07-30  5:31 ` rwild at gcc dot gnu dot org
2004-05-17  4:39 [Bug ada/15479] New: " jsm28 at gcc dot gnu dot org
2004-05-17  4:47 ` [Bug ada/15479] " 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=20080224223836.3027.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).