bzr email commit hook

plugin documentation does not make interaction with checkouts clear

Bug #118626 reported by Stuart Colville
2
Affects Status Importance Assigned to Milestone
bzr email commit hook
Confirmed
Medium
Unassigned

Bug Description

If I configure the email plugin in ~/.bazaar/locations.conf

like so (paths and email addresses changed obviously) it never works

[/Volumes/dir]
post_commit_to = <email address hidden>
post_commit_mailer = smtplib
smtp_server = example.com:25
smtp_username = username

If I configure it with exactly the same details but set the branch as

[*]

The plugin sends a mail.

Revision history for this message
Stuart Colville (muffinresearch) wrote :

I'm using bzr 0.16 on a macbook pro. The bug existed in 0.15 too.

Revision history for this message
Stuart Colville (muffinresearch) wrote :

Ok I've solved my own problem. I was putting the location of the checkout when in fact the location needed to be the remote branch location e.g. sftp://blah.com etc. I'm wondering if the README should be updated to mention this as this is an easy mistake to make.

Revision history for this message
Stuart Colville (muffinresearch) wrote :

Also to clarify other plugins such as the irc plugin and the email (as in whoami) config work using the checkout location and not the branch location.

Revision history for this message
John A Meinel (jameinel) wrote :

This seems to be primarily a documentation bug.

I've found it to be extremely useful to use the source location rather than the checkout location, because it lets me do:

[sftp://host/path/to/base]
public_location = http://host/base
public_location:policy=appendpath

And then *all* of my branches on that public server can send an email with the correct location. (http://host/base/branchname)

But I can respect that it could be documented more clearly.

Also, I would recommend the other plugins switch to the same model.

Changed in bzr-email:
importance: Undecided → Medium
status: Unconfirmed → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.