From: Eric Sandeen <sandeen@sandeen.net>
To: Dave Chinner <david@fromorbit.com>
Cc: Itaru Kitayama <itaru.kitayama@gmail.com>, xfs@oss.sgi.com
Subject: Re: [PATCH] xfstests comma separated group names
Date: Wed, 22 May 2013 09:12:56 -0500 [thread overview]
Message-ID: <519CD268.10306@sandeen.net> (raw)
In-Reply-To: <20130521052118.GM24543@dastard>
On 5/21/13 12:21 AM, Dave Chinner wrote:
> On Tue, May 21, 2013 at 12:45:32PM +0900, Itaru Kitayama wrote:
>> In the current check script the -g option assumes only one group is given.
>> With this patch, the -g option
>> understands comma separated multiple groups as the argument as well.
>> Existing scripts are not affected
>> by this patch.
>>
>> Reviewed-by: Dave Chinner <david@redhat.com>
>
> No, I didn't. A comment on a patch is not a review.
>
> The only time you should add tags like this is if you receive them
> in email from the person in question. Once I've actaully done a
> review of the code, I'll respond with such a tag. See
> Documentation/SubmittingPatches for more information about what the
> reviewed-by tag actually means...
>
>> Signed-off-by: Itaru Kitayama <itaru.kitayama@gmail.com>
>>
>> ---
>>
>> check | 23 ++++++++++++-----------
>> 1 file changed, 12 insertions(+), 11 deletions(-)
>>
>> diff --git a/check b/check
>> index a79747e..0e0f208 100755
>> --- a/check
>> +++ b/check
>> @@ -164,18 +164,19 @@ while [ $# -gt 0 ]; do
>> -nfs) FSTYP=nfs ;;
>>
>> -g) group=$2 ; shift ;
>> - group_list=$(get_group_list $group)
>> - if [ -z "$group_list" ]; then
>> - echo "Group \"$group\" is empty or not defined?"
>> - exit 1
>> - fi
>> -
>> - [ ! -s $tmp.list ] && touch $tmp.list
>> - for t in $group_list; do
>> - grep -s "^$t\$" $tmp.list >/dev/null || \
>> - echo "$t"
>>>> $tmp.list
>
> There's a whitespace and wrapping problem with your mailer. it's
> converting all tabs to spaces, and it's wrapping long lines in the
> patch. Please see Documentation/email-clients.txt for help to set
> your mailer up properly.
Dave is a tough teacher but you can learn a lot from him. ;)
Thanks for sending the patch, I agree that this will be nice to have,
once the patch submission issues get fixed up.
-Eric
> Cheers,
>
> Dave.
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2013-05-22 14:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-20 8:29 [PATCH] xfstests comma separated group names Itaru Kitayama
2013-05-20 11:30 ` Dave Chinner
2013-05-20 11:42 ` Itaru Kitayama
2013-05-21 0:45 ` Dave Chinner
2013-05-21 3:45 ` Itaru Kitayama
2013-05-21 5:21 ` Dave Chinner
2013-05-22 14:12 ` Eric Sandeen [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=519CD268.10306@sandeen.net \
--to=sandeen@sandeen.net \
--cc=david@fromorbit.com \
--cc=itaru.kitayama@gmail.com \
--cc=xfs@oss.sgi.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