From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: Jeff Layton <jlayton@redhat.com>
Cc: Bryan Schumaker <bjschuma@netapp.com>,
Benny Halevy <bhalevy@panasas.com>,
Chuck Lever <chuck.lever@oracle.com>,
Thomas Haynes <thomas@netapp.com>,
linux-nfs@vger.kernel.org
Subject: Re: Patched up cthon source?
Date: Tue, 25 Jan 2011 10:38:32 -0500 [thread overview]
Message-ID: <1295969912.6867.2.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <20110125095649.446212fd@tlielax.poochiereds.net>
On Tue, 2011-01-25 at 09:56 -0500, Jeff Layton wrote:
> On Tue, 25 Jan 2011 08:43:25 -0500
> Bryan Schumaker <bjschuma@netapp.com> wrote:
>
> > On 01/24/2011 05:33 PM, Benny Halevy wrote:
> > > this is a problem with the version of nroff on newer distributions.
> >
> > My version of groff (1.21) is splitting the error into two lines, so I am using the following patch.
> >
> > Bryan
> >
>
> Yep, this workaround stopped working around for me on my rawhide box
> broke yesterday for the same reason.
>
> I think this patch may be a better approach than trying to grep out
> random stuff, but I don't know whether non-GNU tbl programs will barf
> on it. If anyone has a solaris box handy, could you let me know if
> this breaks on it?
>
> ----------------------[snip]------------------
> [PATCH] cthon04: add "nowarn" option to nroff.in tables
>
> This prevents the tbl preprocessor from stuffing warnings into the
> resulting file, which subsequently can make nroff spew warnings like
> this on stderr:
>
> warning: file `nroff.in', around line 47:
> table wider than line width
>
> Unfortunately, I'm not sure how non-gnu tbl programs will react to
> this option, so YMMV.
>
> Signed-off-by: Jeff Layton <jlayton@redhat.com>
> ---
> general/nroff.in | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/general/nroff.in b/general/nroff.in
> index 522ac80..a8acb3a 100644
> --- a/general/nroff.in
> +++ b/general/nroff.in
> @@ -18,7 +18,7 @@ benchmarks.
> .LP
> I ran the benchmarks on the following configurations:
> .TS
> -center;
> +center nowarn;
> l l l l.
> CPU Unix Fortran Memory
> .sp 4p
> @@ -38,7 +38,7 @@ A bubble sort of integers.
> A prime number generator.
> .LP
> .TS
> -center;
> +center nowarn;
> c|c|c s|c s|
> c|c|c s|c s|
> c|c|c s|c s|
Here's a radical idea: what say we change the nroff.in file so that it
no longer tries to fit a 130ish character wide table into an 80
character wide page?
Cheers
Trond
--
Trond Myklebust
Linux NFS client maintainer
NetApp
Trond.Myklebust@netapp.com
www.netapp.com
next prev parent reply other threads:[~2011-01-25 15:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-24 22:19 Patched up cthon source? Thomas Haynes
2011-01-24 22:24 ` Chuck Lever
2011-01-24 22:33 ` Benny Halevy
2011-01-24 23:01 ` Jim Rees
2011-01-24 23:32 ` Thomas Haynes
2011-01-25 13:43 ` Bryan Schumaker
2011-01-25 14:56 ` Jeff Layton
2011-01-25 15:38 ` Trond Myklebust [this message]
2011-01-25 15:46 ` peter.staubach
2011-01-25 15:53 ` Jeff Layton
[not found] ` <20110125095649.446212fd-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2011-02-07 19:13 ` Jim Rees
2011-02-07 22:00 ` Jeff Layton
2011-01-24 22:50 ` sfaibish
2011-01-25 9:46 ` DENIEL Philippe
2011-01-25 17:05 ` Steve Dickson
2011-01-25 21:36 ` Halevy, Benny
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=1295969912.6867.2.camel@heimdal.trondhjem.org \
--to=trond.myklebust@netapp.com \
--cc=bhalevy@panasas.com \
--cc=bjschuma@netapp.com \
--cc=chuck.lever@oracle.com \
--cc=jlayton@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=thomas@netapp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.