Fix incorrect use of loose in hfs.txt
PATCH 1/1 Fix incorrect use of loose in hfs.txt
Fix incorrect use of loose in hfs.txt
It should be 'lose', not 'loose'.
---
Documentation/filesystems/hfs.txt | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-)
Documentation/filesystems/hfs.txt +1 -1
@@ -61,7 +61,7 @@ the a little strange: Finder's metadata. o They are however created (with default values), deleted and renamed along with the corresponding data fork or directory. - o Copying files to a different filesystem will loose those attributes + o Copying files to a different filesystem will lose those attributes that are essential for MacOS to work.
Quoted 6 lines · On Fri, 05 Dec 2008 14:07:58 +1100 Nick Andrew wrote:
Fix incorrect use of loose in hfs.txt
It should be 'lose', not 'loose'.
Signed-off-by Nick Andrew <[email protected]>---
Nick,
For any of these patches that were not picked up/merged/applied by someone, maybe you should resend them to lkml/wherever and cc: [email protected]:
TRIVIAL PATCHES
P: Jiri Kosina
M: [email protected]
L: [email protected]
T: git kernel.org:/pub/scm/linux/kernel/git/jikos/trivial.git
S: Maintained
Quoted 20 lines
Documentation/filesystems/hfs.txt | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-)Documentation/filesystems/hfs.txt +1
-2@@ -61,7 +61,7 @@ the a little strange: Finder's metadata. o They are however created (with default values), deleted and renamed along with the corresponding data fork or directory. - o Copying files to a different filesystem will loose those attributes + o Copying files to a different filesystem will lose those attributes that are essential for MacOS to work. --
Quoted 4 lines
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
---
~Randy
Quoted 2 lines · Randy Dunlap
For any of these patches that were not picked up/merged/applied by someone, maybe you should resend them to lkml/wherever and cc: [email protected]:
Yes, I'll check again in a couple of months. More recently I posted a bunch of typo fixes to lkml + trivial and that's a lot easier for me to do than sending each patch to a maintainer. Any patch which fails to merge due to real work in an affected file can be dropped and resubmitted later.
Nick.