Merge emails blow my mind
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Invalid
|
Wishlist
|
Unassigned | ||
bzr email commit hook |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
The merge email contains an amazing amount of useless information. Here's an example:
De : <email address hidden>
Objet : Rev 2859: [r=BjornT] add a 'priority' sub-command to the email UI in /home/pqm/
Date : November 28, 2005 1:10:56 PM EST (CA)
À : <email address hidden>
Répondre à : <email address hidden>
-------
revno: 2859
revision-id: <email address hidden>
parent: <email address hidden>
parent: <email address hidden>
committer: Canonical.com Patch Queue Manager<email address hidden>
timestamp: Mon 2005-11-28 18:09:09 +0000
message:
[r=BjornT] add a 'priority' sub-command to the email UI
modified:
lib/canonical
lib/canonical
---
merged: <email address hidden>
parent: <email address hidden>
parent: <email address hidden>
committer: Brad Bollenbach <email address hidden>
timestamp: Mon 2005-11-28 12:12:44 -0500
message:
merge from rf, resolving conflicts
---
merged: <email address hidden>
parent: <email address hidden>
committer: Brad Bollenbach <email address hidden>
timestamp: Fri 2005-11-25 17:03:39 -0500
message:
add a 'priority' email sub-command to the Malone email UI
--
arch-commits mailing list
<email address hidden>
http://
Out of this entire blob of information I'm bombarded with, only the Subject line is actually useful, and even then, only half of that, the "Rev 2859: [r=BjornT] add a 'priority' sub-command to the email UI" bit.
I would suggest that all this information be removed from merge mails, unless I explicitly ask for insane verbosity. There are exactly two things I care very much about in a merge notification:
1. The summary message, including who made the change, of course.
2. The diff.
Changed in pqm: | |
status: | New → Rejected |
Le 28-Nov-05 à 4:21 PM, Robert Collins a écrit :
> Public bug report changed: /launchpad. net/malone/ bugs/5140
> https:/
>
> Changed in: PQM (upstream)
> Status: New => Rejected
> Explanation: This is not something PQM knows about - notification
> emails are driven by bzr.
I wouldn't have guessed that initially, but now that seems to make
sense.
Wouldn't it make more sense to retarget this to the bzr product
though, or are you suggesting that my confusion is unwarranted?
Cheers,
--
Brad Bollenbach