From: Stan Shebs <shebs@apple.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb@sources.redhat.com
Subject: Re: [doc/gdbint.texinfo] \xdef\manvers{\$Revision: 1.142 $}
Date: Fri, 15 Jun 2001 11:03:00 -0000 [thread overview]
Message-ID: <7A1.B6616B56@apple.com> (raw)
In-Reply-To: <3B297CFE.4030207@cygnus.com>
Andrew Cagney wrote:
>
> gdb/doc/gdbint.texinfo contains:
>
> > \def\$#1${{#1}} % Kluge: collect RCS revision info without $...$
> > \xdef\manvers{\$Revision: 1.142 $} % For use in headers, footers too
> > {\parskip=0pt
>
> I'm wondering if that should be changed to use gdb/version.in? I guess
> it really depends on what the purpose of it is.
>
> Anyone know?
Without researching it, I'll guess that this is old junk that Gilmore
added long ago, on the theory that cvs commits would result in a new
version number that could show up in a formatted manual. Of course,
since it's for TeX only, doesn't help with info files, web pages (the
web not yet having been invented at the time!), etc.
It would be maximally careful to check that the macro isn't secretly
referenced inside texinfo.tex, but other than that I don't know of a
reason not to just whack this.
Stan
next prev parent reply other threads:[~2001-06-15 11:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-15 0:10 Andrew Cagney
2001-06-15 5:27 ` Eli Zaretskii
2001-06-15 11:03 ` Stan Shebs [this message]
2001-06-27 21:28 ` Andrew Cagney
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=7A1.B6616B56@apple.com \
--to=shebs@apple.com \
--cc=ac131313@cygnus.com \
--cc=gdb@sources.redhat.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