All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Lever <chuck.lever@oracle.com>
To: Steve Dickson <SteveD@redhat.com>
Cc: Linux NFS mailing list <nfs@lists.sourceforge.net>
Subject: Re: [PATCH] export man page updated.
Date: Tue, 18 Sep 2007 11:48:52 -0400	[thread overview]
Message-ID: <46EFF364.7040003@oracle.com> (raw)
In-Reply-To: <46EFB157.4010508@RedHat.com>

[-- Attachment #1: Type: text/plain, Size: 2041 bytes --]

Steve Dickson wrote:
> Chuck Lever wrote:
>> Steve Dickson wrote:
>>> It was pointed that the exportfs man page talks about
>>> the wrong file. In 2.6 kernels the export information
>>> is now kept in /var/lib/nfs/etab not /var/lib/nfs/xtab.
>>>
>>> This patch basically does a 's/xtab/etab' and is relative
>>> to the to the Fedora git tree
>>>
>>> git://git.infradead.org/~steved/nfs-utils.fedora
>>
>> Hrm, an attachment.
> hmm... are you not seeing the attachments inlined?

When I reply the attachment is discarded so I have to do a number of 
steps to quote your patch that wouldn't be necessary if you had inlined 
the patch.  The point of inlining patches rather than attaching them is 
to allow others to quote the patch in their reply with no extra steps. 
And there are tools to import inlined patches -- not sure if they work 
for attachments.

It's a scalability thing when reviewers have to deal with dozens of 
patches a day.

>> @@ -93,8 +93,8 @@ file, so that only default options and options given 
>> on the command
>>  line are used.
>>  .TP
>>  .B -r
>> -Reexport all directories. It synchronizes /var/lib/nfs/xtab
>> -with /etc/exports. It removes entries in /var/lib/nfs/xtab
>> +Reexport all directories. It synchronizes /var/lib/nfs/etab
>> +with /etc/exports. It removes entries in /var/lib/nfs/etab
>>  which are deleted from /etc/exports, and remove any entries from the
>>  kernel export table which are no longer valid.
>>  .TP
>>
>> In this hunk, why isn't the file name bold, like the others?
> Thats the way it was. If its a problem, I'll respin the patch...

See http://www.faqs.org/docs/Linux-mini/Man-Page.html#Q8

"Filenames are always in italics."

I ask "why isn't this filename bold" because the other instances in this 
particular man page are also bold and not italicized...  which is 
marginally incorrect, if not unconventional.

It's hard to say something like this is "a problem" since it is only a 
man page.  But I like to leave things a little cleaner (more correct) 
than when I found them.

[-- Attachment #2: chuck.lever.vcf --]
[-- Type: text/x-vcard, Size: 290 bytes --]

begin:vcard
fn:Chuck Lever
n:Lever;Chuck
org:Oracle Corporation;Corporate Architecture: Linux Projects Group
adr:;;1015 Granger Avenue;Ann Arbor;MI;48104;USA
title:Principal Member of Staff
tel;work:+1 248 614 5091
x-mozilla-html:FALSE
url:http://oss.oracle.com/~cel
version:2.1
end:vcard


[-- Attachment #3: Type: text/plain, Size: 228 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[-- Attachment #4: Type: text/plain, Size: 140 bytes --]

_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2007-09-18 15:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-17 15:34 [PATCH] export man page updated Steve Dickson
2007-09-17 16:46 ` Chuck Lever
2007-09-18 11:07   ` Steve Dickson
2007-09-18 15:48     ` Chuck Lever [this message]
2007-09-18 18:01       ` Steve Dickson

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=46EFF364.7040003@oracle.com \
    --to=chuck.lever@oracle.com \
    --cc=SteveD@redhat.com \
    --cc=nfs@lists.sourceforge.net \
    /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.