From: jacmet at uclibc.org <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/ntfs-3g
Date: Wed, 27 Aug 2008 13:19:01 -0700 (PDT) [thread overview]
Message-ID: <20080827201901.A9ECD3C864@busybox.net> (raw)
Author: jacmet
Date: 2008-08-27 13:19:01 -0700 (Wed, 27 Aug 2008)
New Revision: 23254
Log:
ntfs-3g: fix long help text lines
Modified:
trunk/buildroot/package/ntfs-3g/Config.in
Changeset:
Modified: trunk/buildroot/package/ntfs-3g/Config.in
===================================================================
--- trunk/buildroot/package/ntfs-3g/Config.in 2008-08-27 20:18:58 UTC (rev 23253)
+++ trunk/buildroot/package/ntfs-3g/Config.in 2008-08-27 20:19:01 UTC (rev 23254)
@@ -2,6 +2,11 @@
bool "ntfs-3g"
select BR2_PACKAGE_PKGCONFIG
help
- The NTFS-3G driver is an open source, freely available read/write NTFS driver for Linux, FreeBSD, Mac OS X, NetBSD, and Haiku. It provides safe and fast handling of the Windows XP, Windows Server 2003, Windows 2000 and Windows Vista file systems. Most POSIX file system operations are supported, with the exception of full file ownership and access right support.
+ The NTFS-3G driver is an open source, freely available
+ read/write NTFS driver for Linux, FreeBSD, Mac OS X, NetBSD,
+ and Haiku. It provides safe and fast handling of the Windows
+ XP, Windows Server 2003, Windows 2000 and Windows Vista file
+ systems. Most POSIX file system operations are supported, with
+ the exception of full file ownership and access right support.
http://www.ntfs-3g.org/
next reply other threads:[~2008-08-27 20:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-27 20:19 jacmet at uclibc.org [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-01-10 0:23 [Buildroot] svn commit: trunk/buildroot/package/ntfs-3g ulf at uclibc.org
2008-05-11 6:46 ulf at uclibc.org
2007-11-26 7:13 ulf at uclibc.org
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=20080827201901.A9ECD3C864@busybox.net \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/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