Michael Haggerty <mhagger@xxxxxxxxxxxx> writes: > I would like the checking configuration to be *versioned* along with the > code. For example, suppose my project decides to enforce a rule that > all Python code needs to be indented with spaces. It might be that not > all of our old code adheres to this rule, and that we only want to clean > up the code in master. You want to sneak in a badly formatted code? Add an entry to the in-tree attributes file to disable whitespace checking to cover that file! So even though I agree with you that the check mechanism may need to be aware of what revision it is checking and adjust which rules are applied when checking the revision, I do not think using in-tree attribute file is the right solution to that problem. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html