Or perhaps add a generic mechanism globally or per-rule so ignore certain files. I found myself needing to jump through hoops to ignore logging from some commands.
On Wed, Dec 2, 2015 at 11:04 PM, Mike Shal <[email protected]> wrote: > On Wed, Dec 2, 2015 at 4:49 PM, Stephen Irons <[email protected]> > wrote: > >> >> >> On 3 December 2015 at 06:00, Freddie Chopin <[email protected]> >> wrote: >> >>> >>> You might want to ignore other hidden folders of popular version control >>> systems - ".svn" would be a good candidate. >>> >>> >> Also ".bzr", Canonical's bazaar DVCS. Not really popular, but I use it >> (and tup). >> >> >> > Thanks, I've added .svn & .bzr > > On second thought, should we just be ignoring hidden directories > altogether? This should take care of all of these cases, and probably many > others, but still allow hidden files in non-hidden directories. So > foo/.hidden would be tracked by tup but .hidden/foo would be ignored. > > -Mike > > -- > -- > tup-users mailing list > email: [email protected] > unsubscribe: [email protected] > options: http://groups.google.com/group/tup-users?hl=en > --- > You received this message because you are subscribed to the Google Groups > "tup-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- -- tup-users mailing list email: [email protected] unsubscribe: [email protected] options: http://groups.google.com/group/tup-users?hl=en --- You received this message because you are subscribed to the Google Groups "tup-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
