From: Rich Johnston <rjohnston@sgi.com>
To: zwu.kernel@gmail.com
Cc: Zhi Yong Wu <wuzhy@linux.vnet.ibm.com>, xfs@oss.sgi.com
Subject: Re: [PATCH] xfstests: fix the seq number in README
Date: Mon, 25 Mar 2013 08:52:40 -0500 [thread overview]
Message-ID: <515056A8.8000408@sgi.com> (raw)
In-Reply-To: <1364045391-28476-1-git-send-email-zwu.kernel@gmail.com>
On 03/23/2013 08:29 AM, zwu.kernel@gmail.com wrote:
> From: Zhi Yong Wu <wuzhy@linux.vnet.ibm.com>
>
> Although it is one very trivial bug, one patch is worth to
> make it perfect.
>
> Signed-off-by: Zhi Yong Wu <wuzhy@linux.vnet.ibm.com>
> ---
> README | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/README b/README
> index b70f75d..2d231de 100644
> --- a/README
> +++ b/README
> @@ -177,7 +177,7 @@ Test script environment:
> and the content of the NIS database
> if it is likely to be present)
>
> - 4. General recommendations, usage conventions, etc.:
> + 5. General recommendations, usage conventions, etc.:
> - When the content of the password or group file is
> required, get it using the _cat_passwd and _cat_group
> functions, to ensure NIS information is included if NIS
>
Proper documentation is important thanks for the patch.
This patch has been committed.
Thanks
--Rich
commit dd1ee061a8784520287a7847c3404d719f46c854
Author: Zhi Yong Wu <wuzhy@linux.vnet.ibm.com>
Date: Sat Mar 23 13:29:51 2013 +0000
xfstests: fix the seq number in README
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2013-03-25 13:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-23 13:29 [PATCH] xfstests: fix the seq number in README zwu.kernel
2013-03-23 14:55 ` Eric Sandeen
2013-03-25 13:52 ` Rich Johnston [this message]
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=515056A8.8000408@sgi.com \
--to=rjohnston@sgi.com \
--cc=wuzhy@linux.vnet.ibm.com \
--cc=xfs@oss.sgi.com \
--cc=zwu.kernel@gmail.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