From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
To: linux-mtd@lists.infradead.org
Subject: [PATCH 2/2] --cvs-exclude for mkfs.jffs2
Date: Mon, 28 Nov 2005 21:27:26 -0500 [thread overview]
Message-ID: <v0ek50fasx.fsf@marajade.sandelman.ca> (raw)
[-- Attachment #1: Type: text/plain, Size: 1352 bytes --]
Signed-off-by: Michael Richardson <mcr@sandelman.ca>
---
util/mkfs.jffs2.1 | 8 ++++++++
1 files changed, 8 insertions(+), 0 deletions(-)
applies-to: e5a6153acb76c3bf3984261748386669e80942f2
08193343c2d58ac0da9d62d2ec6173e83feee6ff
diff --git a/util/mkfs.jffs2.1 b/util/mkfs.jffs2.1
index 7e32c92..2340b10 100644
--- a/util/mkfs.jffs2.1
+++ b/util/mkfs.jffs2.1
@@ -34,6 +34,9 @@ mkfs.jffs2 \- Create a JFFS2 file system
.B -b,--big-endian
]
[
+.B --cvs-exclude
+]
+[
.B -D,--devtable=FILE
]
[
@@ -142,6 +145,11 @@ Write \'CLEANMARKER\' nodes with the siz
normally appropriate to specify a size other than the default 12
bytes.
.TP
+.B --cvs-exclude
+When making lists of files ignore CVS control directories. In addition,
+ignore files called ".KEEP_ME" which may have been created solely to prevent
+CVS from pruning directories.
+.TP
.B -n, --no-cleanmarkers
Do not write \'CLEANMARKER\' nodes to the beginning of each erase
block. This option can be useful for creating JFFS2 images for
---
0.99.9.GIT
--
] ON HUMILITY: to err is human. To moo, bovine. | firewalls [
] Michael Richardson, Xelerance Corporation, Ottawa, ON |net architect[
] mcr@xelerance.com http://www.sandelman.ottawa.on.ca/mcr/ |device driver[
] panic("Just another Debian GNU/Linux using, kernel hacking, security guy"); [
[-- Attachment #2: Type: application/pgp-signature, Size: 480 bytes --]
reply other threads:[~2005-11-29 2:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=v0ek50fasx.fsf@marajade.sandelman.ca \
--to=mcr@sandelman.ottawa.on.ca \
--cc=linux-mtd@lists.infradead.org \
/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