From: Rich Johnston <rjohnston@sgi.com>
To: Eryu Guan <eguan@redhat.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] xfstests: add missing colon in _filter_ln
Date: Wed, 29 May 2013 14:45:44 -0500 [thread overview]
Message-ID: <51A65AE8.5010500@sgi.com> (raw)
In-Reply-To: <1369842106-9869-1-git-send-email-eguan@redhat.com>
On 05/29/2013 10:41 AM, Eryu Guan wrote:
> On distros with older coreutils(eg. RHEL5) generic/294 fails like
>
> -ln: creating symbolic link `SCRATCH_MNT/294.test/testlink': File exists
> +ln: creating symbolic link `SCRATCH_MNT/294.test/testlink'File exists
>
> _filter_ln ate the ": ". xfs/103 has similar issue. Add ": " back.
>
> Signed-off-by: Eryu Guan <eguan@redhat.com>
Thanks for the patch, it has been committed:
commit 3f09dca681eb0cdd850abbcdb4d6997a0890b09a
Author: Eryu Guan <eguan@redhat.com>
Date: Wed May 29 14:42:09 2013 -0500
xfstests: add missing colon in _filter_ln
--Rich
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2013-05-29 19:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-29 15:41 [PATCH] xfstests: add missing colon in _filter_ln Eryu Guan
2013-05-29 16:21 ` Eric Sandeen
2013-05-29 19:45 ` 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=51A65AE8.5010500@sgi.com \
--to=rjohnston@sgi.com \
--cc=eguan@redhat.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