On Thu, Sep 10, 2015 at 3:33 PM, Markus Heidelberg <markus.heidelb...@web.de > wrote:
> Am Donnerstag, 10. September 2015, 14:33:37 schrieb Manuel Ortega: > > In the case of mercurial, there's no need to make branches or merges in > > order to solve this problem. Just add the following to $REPO/.hg/hgrc: > > > > [hooks] > > pre-status = hg revert runtime/doc/tags > > pre-update = hg revert runtime/doc/tags > > pre-pull = hg revert runtime/doc/tags > > > > I'm about to investigate whether (a) something similar can done in git, > and > > (b) if the answer is yes, whether Bram can set it in the GitHub repo and > > have it percolate down to all of us. > > In Git you can use hooks as well, see githooks(5). > > But generally hooks cannot be deployed via VCS because automatically > invoking scripts would be a security concern. I found `man githooks`, but there don't appear to exist the right kind of hooks to pull this off. -Manny -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
