summaryrefslogtreecommitdiff
path: root/debian/FAQ
diff options
context:
space:
mode:
authormadduck <madduck@3cfab66f-1918-0410-86b3-c06b76f9a464>2006-10-24 09:09:16 +0000
committermadduck <madduck@3cfab66f-1918-0410-86b3-c06b76f9a464>2006-10-24 09:09:16 +0000
commit3a102a0b6737149e97b69f59f2f6bc6e1331e87a (patch)
tree324c1c17c58400f8d5cf1ead34c03ebf8799413b /debian/FAQ
parent73731ad40c861d37adb7fee3620923e01f4e0fed (diff)
i am not the upstream maintainer
Diffstat (limited to 'debian/FAQ')
-rw-r--r--debian/FAQ2
1 files changed, 1 insertions, 1 deletions
diff --git a/debian/FAQ b/debian/FAQ
index 6f5cc7f9..0330eebd 100644
--- a/debian/FAQ
+++ b/debian/FAQ
@@ -191,7 +191,7 @@ Also see /usr/share/doc/mdadm/README.recipes.gz
The advantage of far= is that you can easily spread a long sequential read
across the drives. The cost is more seeking for writes. offset= can
possibly get similar benefits with large enough chunk size. Neither upstream
- nor the upstream maintainer have tried to understand all the implications of
+ nor the package maintainer have tried to understand all the implications of
that layout. It was added simply because it is a supported layout in DDF and
DDF support is a goal.