Emily Shaffer <emilyshaffer@xxxxxxxxxx> writes: >> So, a Porcelain script cannot learn where the hook command comes >> from, > > Not as I had envisioned. > >> or what the precedence order of each line of the output is? >> > > They're printed in the order they should be executed; the explicit order > isn't provided. > > > I suppose I had considered really just the one use case listed in the > commit message, especially since other inquiry into the hooks to be run > can be done against the config files themselves. But - I'm of course > open to use cases. What did you have in mind? A tool to diagnose why the hooks are not firing in the order the user intended them to, for example? Or a tool to help editing the list of hooks.
