> One of the key elements here is the way we use python-checkins for > after-the-fact review. I think this can be achieved with a better email hook. I would propose that there will be one email message per push per branch (rather than one per changeset). For each branch, it should report what changesets contributed, and what the final diff between the old head of the branch and the new head of the branch is. Or perhaps put the diffs into attachments, one per branch. Or perhaps suppress the diffs for the branches if the only changesets on the branches are merges. In the rare case that a single push includes unrelated changes, people can still look at the individual changesets in the repo to figure it all out. Regards, Martin
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4