From: Jim Meyering Date: Wed, 25 Mar 1998 07:38:24 +0000 (+0000) Subject: s/@samp/@email/ for e-mail addresses X-Git-Tag: TEXTUTILS-1_22f~146 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=cbf0181378e63773c5d23a7032423feba3519e9b;p=thirdparty%2Fcoreutils.git s/@samp/@email/ for e-mail addresses --- diff --git a/doc/getdate.texi b/doc/getdate.texi index b0cb1d272f..09c690a464 100644 --- a/doc/getdate.texi +++ b/doc/getdate.texi @@ -467,15 +467,15 @@ year. @cindex MacKenzie, David @cindex Meyering, Jim @code{getdate} was originally implemented by Steven M. Bellovin -(@samp{smb@@research.att.com}) while at the University of North Carolina +(@email{smb@@research.att.com}) while at the University of North Carolina at Chapel Hill. The code was later tweaked by a couple of people on -Usenet, then completely overhauled by Rich $alz (@samp{rsalz@@bbn.com}) -and Jim Berets (@samp{jberets@@bbn.com}) in August, 1990. Various +Usenet, then completely overhauled by Rich $alz (@email{rsalz@@bbn.com}) +and Jim Berets (@email{jberets@@bbn.com}) in August, 1990. Various revisions for the GNU system were made by David MacKenzie, Jim Meyering, and others. @cindex Pinard, F. @cindex Berry, K. This chapter was originally produced by Fran@,{c}ois Pinard -(@samp{pinard@@iro.umontreal.ca}) from the @file{getdate.y} source code, -and then edited by K.@: Berry (@samp{kb@@cs.umb.edu}). +(@email{pinard@@iro.umontreal.ca}) from the @file{getdate.y} source code, +and then edited by K.@: Berry (@email{kb@@cs.umb.edu}). diff --git a/doc/textutils.texi b/doc/textutils.texi index b96605799b..91329ec53a 100644 --- a/doc/textutils.texi +++ b/doc/textutils.texi @@ -142,7 +142,7 @@ The GNU text utilities are mostly compatible with the @sc{POSIX.2} standard. @c This paragraph appears in all of fileutils.texi, textutils.texi, and @c sh-utils.texi too -- so be sure to keep them consistent. @cindex bugs, reporting -Please report bugs to @samp{textutils-bugs@@gnu.org}. Remember +Please report bugs to @email{textutils-bugs@@gnu.org}. Remember to include the version number, machine architecture, input files, and any other information needed to reproduce the bug: your input, what you expected, what you got, and why it is wrong. Diffs are welcome, but