From: David Chinner <dgc@sgi.com>
To: Christoph Hellwig <hch@lst.de>
Cc: xfs@oss.sgi.com
Subject: Re: new xfsqa mismatches
Date: Tue, 8 Apr 2008 07:55:39 +1000 [thread overview]
Message-ID: <20080407215539.GC108924158@sgi.com> (raw)
In-Reply-To: <20080407100140.GA11891@lst.de>
On Mon, Apr 07, 2008 at 12:01:40PM +0200, Christoph Hellwig wrote:
> 103:
>
> - output mismatch (see 103.out.bad)
> 7c7
> < ln: creating symbolic link `SCRATCH_MNT/nosymlink/target' to `SCRATCH_MNT/nosymlink/source': Operation not permitted
> ---
> > ln: creating symbolic link `SCRATCH_MNT/nosymlink/target' to `SCRATCH_MNT/nosymlink/source' to `SCRATCH_MNT/nosymlink/source': Operation not permitted
>
> not sure where the double to comes from but we should catch it
>From the last fix that I did to fix this for new version of ln.
If other ppl sent xfsqa patches to the oss list, then you'd see that
a patch to fix this was sent out for review yesterday....
> 130 and 132 expetect Bytes in various places but get bytes from xfs_io
> from CVS
What's the error output? I've not seen that one....
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
next prev parent reply other threads:[~2008-04-07 21:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-07 10:01 new xfsqa mismatches Christoph Hellwig
2008-04-07 21:55 ` David Chinner [this message]
2008-04-08 10:41 ` 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=20080407215539.GC108924158@sgi.com \
--to=dgc@sgi.com \
--cc=hch@lst.de \
--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