On Sun, Oct 12, 2008 at 3:31 AM, Brian May
<address@hidden> wrote:
Derek Scherger wrote:
I had an idea the other day, where I was continually having to provide a bunch of --exclude optons in a workspace with some (intentionally) missing files, that it might be useful to be able to specify a set of includes or excludes that persist across several commands. This would avoid the need to repeatedly specify the set of paths to include or exclude. It turns out to be very simple to implement and I have a the basics working so I thought I'd check and see if people would generally find this good, bad or ugly.
This change isn't about ignoring unversioned files but about temporarily ignoring changes to versioned files. I.e. restricting status/diff/commit/etc. to specified sets of files, which is already possible with command line path arguments. This just allows for a persistent selection of changed files so that several status/diff/etc. commands can be executed without having to specify the same set of paths every time. It also allows for successive refinement of the set of included/excluded files.
Cheers,
Derek