Trouble Setting up email notifications
Greg Ward
greg-hg at gerg.ca
Wed Aug 24 23:59:53 UTC 2011
2011/8/24 <charlie at thegallos.com>:
> ...snip...
>> .hg/hgrc <- correct
>> .hg/.hgrc <- incorrect
> ...snip...
>
> That helped a LOT, but Mercurial started throwing a parse error, which I
> have now handled (and submitted) - still not getting emails - but that
> might be 'other' issues
"hg --debug push ..." is often illuminating.
Likewise "hg showconfig" -- run that *in the target repo* and see if
hg really sees the config you think it is seeing.
Alternately, if you want to concentrate on the target repo and get
away from the source (client) repo, you can use bundles to split the
push process up a bit. On the client:
hg commit -m"whatever" # garbage changeset for testing
hg bundle outgoing.bundle
Think of "hg bundle" as "push to a file" (as opposed to "push over the
wire to another repo"). Copy outgoing.bundle to the server where your
target repo lives. cd into the target repo and run
hg --debug unbundle outgoing.bundle
Then you *only* see the debug output related to applying the new
changesets to your target repo. You don't get distracted by the
verbose debug output of a full push. And you can repeat the process
several times. If notify doesn't work, just rollback the unbundle
transaction and try again.
And, oh yeah, you really should be doing this in a *test* target repo,
not your production repo!
Greg
More information about the Mercurial
mailing list