Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: aj@suse.de, ian@airs.com, gcc-patches@gcc.gnu.org,
	 gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix deftypefn in fopen_unlocked.c
Date: Sun, 15 May 2005 20:16:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.61.0505151949500.5856@digraph.polyomino.org.uk> (raw)
In-Reply-To: <01c55985$Blat.v2.4$50507620@zahav.net.il>

On Sun, 15 May 2005, Eli Zaretskii wrote:

> > (and it should be verified that the new functions.texi does indeed
> > pass "make info" and "make dvi" before committing it).
> 
> I verified the former before I submitted the patches.  As for the
> latter, unless someone is going to preview the DVI output and make
> sure it looks okay in print, "make info" can be regarded as a
> good-enough test for "make dvi" as well.

On the contrary, many times patches have broken "make dvi" but passed 
"make info".  See the last such breakage in libiberty 
<http://gcc.gnu.org/ml/gcc-patches/2005-03/msg02853.html> for an example.  
"make info" and "make dvi" detect different subsets of invalid Texinfo; 
http://gcc.gnu.org/contribute.html specifies both for documentation 
patches for a reason.

-- 
Joseph S. Myers               http://www.srcf.ucam.org/~jsm28/gcc/
    jsm@polyomino.org.uk (personal mail)
    joseph@codesourcery.com (CodeSourcery mail)
    jsm28@gcc.gnu.org (Bugzilla assignments and CCs)


  reply	other threads:[~2005-05-15 19:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-14  9:23 Eli Zaretskii
2005-05-15 16:37 ` Ian Lance Taylor
2005-05-15 17:04   ` Andreas Jaeger
2005-05-15 17:44     ` Joseph S. Myers
2005-05-15 18:08       ` Andreas Jaeger
2005-05-15 19:46       ` Eli Zaretskii
2005-05-15 20:16         ` Joseph S. Myers [this message]
2005-05-15 22:09           ` Eli Zaretskii
2005-05-15 22:05       ` Andreas Jaeger
2005-05-16  1:24         ` Eli Zaretskii

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=Pine.LNX.4.61.0505151949500.5856@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=aj@suse.de \
    --cc=eliz@gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=ian@airs.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