[Python-Dev] Hg: inter-branch workflow (original) (raw)
Nick Coghlan ncoghlan at gmail.com
Thu Mar 17 11:49:17 CET 2011
- Previous message: [Python-Dev] Hg: inter-branch workflow
- Next message: [Python-Dev] Hg: inter-branch workflow
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, Mar 17, 2011 at 6:28 AM, Georg Brandl <g.brandl at gmx.net> wrote:
Am 17.03.2011 09:57, schrieb Eric Smith:
On 3/16/2011 11:58 PM, Jesus Cea wrote:
I agree that half the changesets are merges now.
Which has basically stopped me from reviewing changes. I can't quickly tell the real changes from the noise of merges. Even though every merge changeset mail has "merge" in its subject?
I just set up a mail rule to further split up python-checkins email so that they all get tagged with "python-checkins-all", while only those that aren't merges get tagged with "python-checkins". That should make the latter far less noisy than it has been.
Also, we don't really have more revisions than before: for every merge now we typically had a svnmerge then. (Or not, in which case a bugfix wasn't applied to a branch just because it would have been a bother.)
I think it has been exacerbated by the flurry of activity from the sprints. It should be less noticeable once things settle down.
Cheers, Nick.
-- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
- Previous message: [Python-Dev] Hg: inter-branch workflow
- Next message: [Python-Dev] Hg: inter-branch workflow
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]