From: Eric Sandeen <sandeen@sandeen.net>
To: rjohnston@sgi.com
Cc: xfs@oss.sgi.com, linux-ext4@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] cleanup duplicates in all tests
Date: Wed, 03 Apr 2013 15:36:22 -0500 [thread overview]
Message-ID: <515C92C6.8010506@sandeen.net> (raw)
In-Reply-To: <20130403173245.376605011@sgi.com>
On 4/3/13 12:31 PM, rjohnston@sgi.com wrote:
> There are duplicate blank lines, comment hash and lines
> containing duplicate seqres= declarations, remove them.
>
> Signed-off-by: Rich Johnston <rjohnston@sgi.com>
>
> ---
> tests/btrfs/254 | 3 ---
> tests/btrfs/264 | 4 ----
> tests/btrfs/265 | 3 ---
> tests/btrfs/276 | 3 ---
> tests/btrfs/284 | 3 ---
nothing but dup line removal:
$ egrep "^[-+][a-z]" bigpatch | sort | uniq
-seqres=$RESULT_DIR/$seq
and every file still has one left:
$ for FILE in `guilt files`; do grep -c "seqres=$RESULT_DIR" $FILE; done | sort | uniq
1
Looks good to me! :)
Reviewed-by: Eric Sandeen <sandeen@redhat.com>
Thanks,
-Eric
next prev parent reply other threads:[~2013-04-03 20:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-03 17:31 [PATCH] cleanup duplicates in all tests rjohnston
2013-04-03 20:36 ` Eric Sandeen [this message]
2013-04-04 11:59 ` Rich Johnston
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=515C92C6.8010506@sandeen.net \
--to=sandeen@sandeen.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=rjohnston@sgi.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;
as well as URLs for NNTP newsgroup(s).