From: Christoph Hellwig <hch@infradead.org>
To: xfs@oss.sgi.com
Subject: [PATCH] xfstests: fix comment typos in test 201
Date: Sat, 14 Feb 2009 11:39:17 -0500 [thread overview]
Message-ID: <20090214163917.GA19813@infradead.org> (raw)
Signed-off-by: Christoph Hellwig <hch@lst.de>
Index: xfstests-dev/201
===================================================================
--- xfstests-dev.orig/201 2009-02-14 15:06:31.000000000 +0000
+++ xfstests-dev/201 2009-02-14 15:06:42.000000000 +0000
@@ -1,13 +1,13 @@
#! /bin/sh
# FS QA Test No. 201
#
-# Test out the infamout xfs_btree_delrec corruption.
+# Test out the infamous xfs_btree_delrec corruption.
#
# Only happens on 32-bit kernels without CONFIG_LBD, but it should be harmless
# to run this everywhere.
#
#-----------------------------------------------------------------------
-# Copyright (c) 2001 Christoph Hellwig.
+# Copyright (c) 2009 Christoph Hellwig.
#-----------------------------------------------------------------------
#
# creator
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2009-02-14 16:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-14 16:39 Christoph Hellwig [this message]
2009-02-14 19:13 ` [PATCH] xfstests: fix comment typos in test 201 Eric Sandeen
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=20090214163917.GA19813@infradead.org \
--to=hch@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox