{"thread":{"id":"34824","subject":"[RFC] Running a hook on reset","startedAt":"2013-09-01T12:17:11Z","lastAt":"2013-09-01T12:17:11Z","messageCount":1,"participants":["Andres Freund"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"226485","messageId":"20130901121711.GC5695@awork2.anarazel.de","threadId":"34824","inReplyTo":null,"subject":"[RFC] Running a hook on reset","fromName":"Andres Freund","fromEmail":"andres@anarazel.de","sentAt":"2013-09-01T12:17:11Z","receivedAt":"2013-09-01T12:17:11Z","isPatch":false,"sender":{"key":"andres@anarazel.de","avatar":null},"body":"Hi,\n\nI propose adding a hook that is run after git reset.\n\nMy personal use case for that is that I am indexing my checkouts using\nglobal (a tool similar to ctags, cscope, ...)  and I really like that\nindex to be up2date all the time. I can catch most cases where the work\ntree changes from git via the post-checkout, post-merge, post-rewrite\nhooks. The only frequent case I don't know how to trigger a reindex is\ngit reset --hard.\nAnother related usecases I can imagine is people wanting to check that\nthere is nothing important/irrecoverable in the current checkout before\nresetting it, but that would obviously be a pre-reset hook.\n\nAny opinions about the feature before I start writing a patch?\n\nGreetings,\n\nAndres Freund\n"}]}