All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rich Johnston <rjohnston@sgi.com>
To: <xfs@oss.sgi.com>
Cc: <linux-ext4@vger.kernel.org>, <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] cleanup duplicates in all tests
Date: Thu, 4 Apr 2013 06:59:56 -0500	[thread overview]
Message-ID: <515D6B3C.5070104@sgi.com> (raw)
In-Reply-To: <20130403173245.376605011@sgi.com>

Thanks for the review Eric, this patch has been committed.

--Rich

commit 0efd4f4d483a725212f531bc2ed964de2766b1cd
Author: Rich Johnston <rjohnston@sgi.com>
Date:   Wed Apr 3 17:31:49 2013 +0000

     xfstests: cleanup duplicates in all tests

     There are duplicate blank lines, comment hash and lines
     containing duplicate seqres= declarations, remove them.

WARNING: multiple messages have this Message-ID (diff)
From: Rich Johnston <rjohnston@sgi.com>
To: xfs@oss.sgi.com
Cc: linux-ext4@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] cleanup duplicates in all tests
Date: Thu, 4 Apr 2013 06:59:56 -0500	[thread overview]
Message-ID: <515D6B3C.5070104@sgi.com> (raw)
In-Reply-To: <20130403173245.376605011@sgi.com>

Thanks for the review Eric, this patch has been committed.

--Rich

commit 0efd4f4d483a725212f531bc2ed964de2766b1cd
Author: Rich Johnston <rjohnston@sgi.com>
Date:   Wed Apr 3 17:31:49 2013 +0000

     xfstests: cleanup duplicates in all tests

     There are duplicate blank lines, comment hash and lines
     containing duplicate seqres= declarations, remove them.

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  parent reply	other threads:[~2013-04-04 11:59 UTC|newest]

Thread overview: 5+ 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
2013-04-03 20:36   ` Eric Sandeen
2013-04-04 11:59 ` Rich Johnston [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=515D6B3C.5070104@sgi.com \
    --to=rjohnston@sgi.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --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 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.