From: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: Gerald Pfeifer <gerald@pfeifer.com>, gcc-patches@gcc.gnu.org
Subject: Re: updating texinfo.tex
Date: Tue, 18 Mar 2008 20:01:00 -0000 [thread overview]
Message-ID: <20080318192408.GE2094@ins.uni-bonn.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0803181250530.6696@digraph.polyomino.org.uk>
* Joseph S. Myers wrote on Tue, Mar 18, 2008 at 01:52:17PM CET:
> On Tue, 18 Mar 2008, Gerald Pfeifer wrote:
> > On Mon, 17 Mar 2008, Ralf Wildenhues wrote:
> > >
> > > So, ok to update codingconventions.html as below, and ok to update
> > > texinfo.tex, 4.4 and 4.3 branch?
> >
> > I think both the update and the addtion to codingconventions.html are
> > fine. Any objections, Joseph?
>
> It seems fine with me; I was already thinking of texinfo.tex as under the
> rules for importing externally maintained files, even if not explicitly
> listed. (Updates to texinfo.tex should of course be tested with "make
> dvi" or "make pdf".)
Tested both, installed both.
Thanks to both of you!
Ralf
prev parent reply other threads:[~2008-03-18 19:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-18 0:50 Ralf Wildenhues
2008-03-18 5:35 ` Gerald Pfeifer
2008-03-18 13:01 ` Joseph S. Myers
2008-03-18 20:01 ` Ralf Wildenhues [this message]
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=20080318192408.GE2094@ins.uni-bonn.de \
--to=ralf.wildenhues@gmx.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).