From: Steve Dickson <steved@redhat.com>
To: Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: [PATCH 0/3] Connectathon: Remove warning from general tests
Date: Thu, 27 Jan 2011 13:49:31 -0500 [thread overview]
Message-ID: <1296154174-13076-1-git-send-email-steved@redhat.com> (raw)
Here are three approaches to removing the
warning: around line 47: table wider than line width
that is currently occurring in the general tests.
The first approach is to make the stat command, which read
the output time file, ignore lines it does not understand.
The second approach was to fix the nroff.in file. It turns
out, the only I could stop that warning was to decrease the
width of the table. Through my trials and tribulations with
this, I'm beginning to believe the generating of this warning
is a bug in the groff command, since I can not find anything
wrong with the original table definition.
The third and final approach is a patch that Jeff Layton
purposed that leaves the table width alone and adds the
"nowarn" to the global options of the table.
All three seem to do the trick but obviously we don't need
all three... I am leaning towards the first approach since
its not dependent on nroff/tbl isms...
Steve Dickson (2):
Make the stat command ignore lines that it is not looking for.
Make the tbl table smaller to avoid a warning about line width
Jeff Layton (1):
cthon04: add "nowarn" option to nroff.in tables
general/nroff.in | 2 +-
general/stat.c | 9 +++++++--
2 files changed, 8 insertions(+), 3 deletions(-)
--
1.7.3.3
next reply other threads:[~2011-01-27 18:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-27 18:49 Steve Dickson [this message]
2011-01-27 18:49 ` [PATCH 1/3] Make the stat command ignore lines that it is not looking for Steve Dickson
2011-01-27 18:49 ` [PATCH 2/3] Make the tbl table smaller to avoid a warning about line width Steve Dickson
2011-01-27 18:49 ` [PATCH 3/3] cthon04: add "nowarn" option to nroff.in tables Steve Dickson
2011-01-28 2:11 ` Jeff Layton
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=1296154174-13076-1-git-send-email-steved@redhat.com \
--to=steved@redhat.com \
--cc=linux-nfs@vger.kernel.org \
/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 NNTP newsgroup(s).