[Bug 18366] Also commit mail for lock/unlock

2010-05-03 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=18366 Chad H. changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

[Bug 18366] Also commit mail for lock/unlock

2010-05-03 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=18366 Aryeh Gregor changed: What|Removed |Added CC||simetrical+wikib...@gmail.c

[Bug 18366] Also commit mail for lock/unlock

2010-05-02 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=18366 Chad H. changed: What|Removed |Added CC||innocentkil...@gmail.com --- Comment #3 from

[Bug 18366] Also commit mail for lock/unlock

2009-04-08 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=18366 --- Comment #2 from Siebrand 2009-04-08 22:03:37 UTC --- Don't mind which one is chosen. No locks, means no surprises. Commit mail with locks enabled means one could have known. Recently Tim locked something in SecurePoll, and I locked s

[Bug 18366] Also commit mail for lock/unlock

2009-04-08 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=18366 --- Comment #1 from Brion Vibber 2009-04-08 21:40:13 UTC --- I'd be more inclined to disable locks; they don't seem particularly desirable. :P Looks like either way will take a pre-lock hook script? -- Configure bugmail: https://bugzi