Michael J Gruber <git@xxxxxxxxxxxxxxxxxxxx> writes: > Junio C Hamano venit, vidit, dixit 16.06.2016 19:06: > >> I am not so imaginative, either. One remotely plausible use case may >> be a project that has two classes of paths (let's call these classes >> sensitive and others), and requires its participants to sign commits >> that touch sensitive paths. The user needs something finter grained >> than per-project commit.gpgSign there. >> ... >> So, I dunno, either. > > While I follow both of your lines of argumentation, I tend to claim that > they imply: there is no reason to blindly sign any commit... We should > dump that config :) ... no reason to blindly sign any commit IN SUCH A PROJECT that wants you to selectively sign commits. That does not lead to "we should dump that config" that all, does it? -- 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