On Wed, Oct 18, 2006 at 10:07:26PM -0700, Danek Duvall wrote: > So are we keeping track of who's pulling the gate, or at least when the > gate is pulled? One of the ways I decide whether to do a backout or an > undo is to look to see how many people have pulled the changes. If the > changes are severe enough to require an undo, then I notify the people who > pulled the undone change, and tell them how to handle it (unless it's just > the typical small set of people who bringover on every putback, and know > what to do). It'd be nice to be able to do the same thing for the external > mercurial gate. > > Will undo notifications be sent to the notify alias, too?
At the moment, we don't do any tracking of when or who is pulling clones of the gate. I've currently got Teamware undo actions mapped to an 'hg backout'. A direct 1:1 map would have mapped it probably to a 'hg rollback && hg revert' - but I thought it would be easier (at least for now) to map it to 'hg backout'. While this isn't ideal in that it introduces a spurious changeset, it makes it far easier to manage children that we don't want to "abandon" in the case of an undo. Since we map them to a 'backout', there will be a subsequent notification corresponding to the backout sent to the notification alias. cheers, steve -- stephen lau // [EMAIL PROTECTED] | 650.786.0845 | http://whacked.net opensolaris // solaris kernel development _______________________________________________ tools-discuss mailing list tools-discuss@opensolaris.org
