Independently of the other long thread, I'd like to express my love of
the commit queue. It is actually quite a nice feature for someone like
myself who is off in a corner.
I don't want commit access. I'd rather my changes go through some
process like the commit queue to ensure that it doesn't
On Jul 9, 2010, at 3:38 AM, Alex Milowski wrote:
Being able to go around the commit queue means you can cheat. That
seems like something that should be reserved for more severe problems
where we know the process used by the commit queue will fail.
That is not how I see it at all. And calling
On Fri, Jul 9, 2010 at 3:39 PM, Timothy Hatcher timo...@apple.com wrote:
On Jul 9, 2010, at 3:38 AM, Alex Milowski wrote:
Being able to go around the commit queue means you can cheat. That
seems like something that should be reserved for more severe problems
where we know the process used by
On Fri, Jul 9, 2010 at 7:39 AM, Timothy Hatcher timo...@apple.com wrote:
Some of the glaring reasons I don't use the commit queue have been resolved
(svn blame mainly), but the fact that there is no control over when the path
lands is my chief reason.
I agree. When my patch has a potential
4 matches
Mail list logo
