Re: [PATCH 1/2] --cvs-exclude for mkfs.jffs2

[Michael Richardson <mcr@sandelman.ottawa.on.ca>]

[-- Attachment #1: Type: text/plain, Size: 1303 bytes --]


>>>>> "Josh" == Josh Boyer <jwboyer@gmail.com> writes:
    >> I believe the answer is "not".

    Josh> To clarify, the answer is no because you've hard coded this exclude
    Josh> stuff in the tool itself.  Making a more generic --exclude which
    Josh> reads what to exclude from a file might be an option that is
    Josh> acceptable. Then for your specific case you could simply have "CVS"
    Josh> and ".KEEP_ME" listed there.

  Thank you --- I appreciate constructive feedback! 

  I'm happy to do a proper --exclude. I would have rather done it that way to
begin with, but it was hard to hack up in a moment. I posted because I wanted
to clear my queue of patches.
  I would propose, like rsync:
        --exclude=glob
        --exclude-from=FILE
        --scm-exclude=FILE                         

  Last one could be set to, for instance:
           --scm-exclude=.cvsignore
 
  (and could occur multiple times)

  [did my patch to create jffs2cpio make it out?]

-- 
]       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 --]