Emily Shaffer <emilyshaffer@xxxxxxxxxx> writes: > Thanks for the patience with the long wait, all. Here's an attempt at > the rewrite in C; I think it does verbatim what the sh version did > except that this doesn't print the reflog - Jonathan Nieder was good > enough to point out to me that folks probably don't want to share their > commit subjects all willy-nilly if they're working on something > secretive. Is the goal to give a tool the end users can type "git bugreport<RET>" and automatically send the result to this mailing list (or some bug tracker)? Or is this only about producing a pre-filled bug report template to be slurped into their MUA and then further manually edited before sending it out? It probably is controversial if we exposed contents of hooks scripts (I can imagine some people may trigger external process by pinging a URL that includes credential material out of laziness), so the presence test you have is probably a good stopping point. I do not know how much it helps to know which hooks exist in order to diagnose an anomaly without knowing what their contents are, but it is a start. By the way, I doubt that it is the best use of developer time to write these in C---taking various pieces of information from different places to prepare a text file sounds more suited to scripting languages, especially while we are still learning what kind of information we want to collect and how we want to present the final result (iow, for the first handful of years after deploying this command). Thanks.
