On Wed, Feb 8, 2017 at 9:39 PM, Bob Proulx <[email protected]> wrote: > Hello Carl, > > carl hansen wrote: > > still still not working > > Sorry there has been delays. We have been overwhelmed trying to > juggle too many things. > > ​I know the feeling. Luckily it doesn't matter. ​
> I would love to help fix your hook problem. But I enter this knowing > nothing about bzr. I've never used bzr before. I poke into your bzr > repository and explore. > > vcs:/srv/bzr/gsrc# grep -rl gsrc-commit . > ./trunk/.bzr/branch/branch.conf > > vcs:/srv/bzr/gsrc# cat ./trunk/.bzr/branch/branch.conf > last_revision_mailed = [email protected] > orqjagls9tgp1noq > post_commit_to = [email protected] > post_commit_body = "" > post_commit_subject = $nick r$revision: $message > > Okay. That seems to be the configuration for it. But how does that > even do anything? I was expecting to see a hooks directory or > something. Searching the web for documentation on setting up bzr > hooks did not yield anything useful to me. > > Do you know how hook scripts with bzr work? Perhaps you can help me > help you. > > Bob > ​Ok I am poking around. ​$ bzr help hooks spits out some text including: "post_commit ~~~~~~~~~~~ Introduced in: 2.0 Called after a commit is performed on a tree. The hook is called with a bzrlib.mutabletree.PostCommitHookParams object. The mutable tree the commit was performed on is available via the mutable_tree attribute of that object." <message sent to someone who might know more.>
