From: Carlos Maiolino <cmaiolino@redhat.com>
To: Mark Tinguely <tinguely@sgi.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] xfstests 278: Ensure lost+found is not created with wrong link count (V3)
Date: Thu, 12 Jan 2012 09:05:23 -0200 [thread overview]
Message-ID: <20120112110523.GA1798@andromeda.usersys.redhat.com> (raw)
In-Reply-To: <4F0E0A19.6020305@sgi.com>
> >+xfs_repair $SCRATCH_DEV&>> $seq.full
>
> Reviewed-by: Mark Tinguely <tinguely@sgi.com>
>
> As mentioned before, &>> does not work on bash 3.x, the test looks good.
>
Yes, Mark and I discussed about it, but, since the patch is going upstream, I
thought would be better to leave it as-is, once most newer distros are using
bash 4, but, I have no concerns in change it if needed.
Cheers
--
--Carlos
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-01-12 11:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-11 13:35 [PATCH] xfstests 278: Ensure lost+found is not created with wrong link count (V3) Carlos Maiolino
2012-01-11 22:15 ` Mark Tinguely
2012-01-12 11:05 ` Carlos Maiolino [this message]
2012-01-12 13:13 ` Christoph Hellwig
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=20120112110523.GA1798@andromeda.usersys.redhat.com \
--to=cmaiolino@redhat.com \
--cc=tinguely@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