One of the reasons for --include / --exclude is the default handling for non-specific names, ones without + or -, say the output of find or similar, so I'm happy with that scenario. A lot of tools I use have similar semantics.
One set of semantics I would like to explore is to do away with --in/exclude-filename and go with just --in/exclude <spec> where <spec> is: 1) simple filename or directory name 2) @filename to in/exclude by filename 3) - (dash) to in/exclude by stdin To answer edso's next proposal we could make it --filename if we went with --filename <spec> where <spec> is like above but preceded by '+' for inclusion and '-' for exclusion. To avoid confusion we could always drop #3 above. I know of no use for that option in real life. On Fri, Mar 13, 2015 at 7:22 AM, <[email protected]> wrote: > The proposal to merge lp:~aaron-whitehouse/duplicity/filelist_combine into > lp:duplicity has been updated. > > Status: Needs review => Merged > > For more details, see: > > https://code.launchpad.net/~aaron-whitehouse/duplicity/filelist_combine/+merge/252814 > -- > Your team duplicity-team is requested to review the proposed merge of > lp:~aaron-whitehouse/duplicity/filelist_combine into lp:duplicity. > > _______________________________________________ > Mailing list: https://launchpad.net/~duplicity-team > Post to : [email protected] > Unsubscribe : https://launchpad.net/~duplicity-team > More help : https://help.launchpad.net/ListHelp > -- https://code.launchpad.net/~aaron-whitehouse/duplicity/filelist_combine/+merge/252814 Your team duplicity-team is requested to review the proposed merge of lp:~aaron-whitehouse/duplicity/filelist_combine into lp:duplicity. _______________________________________________ Mailing list: https://launchpad.net/~duplicity-team Post to : [email protected] Unsubscribe : https://launchpad.net/~duplicity-team More help : https://help.launchpad.net/ListHelp
