[llvm-commits] [llvm] r71013 - in /llvm/trunk: lib/Transforms/Scalar/LoopStrengthReduce.cpp test/Transforms/LoopStrengthReduce/2009-05-04-Overflow.ll

Bill Wendling isanbard at gmail.com
Wed May 6 13:04:03 PDT 2009


On Wed, May 6, 2009 at 12:42 PM, David A. Greene <greened at obbligato.org> wrote:
> Which I did.  I missed the failure among the noise of all the other failures.
>
> As for the time to respond, you have to consider that we all have work
> meetings, etc. during the day and we won't necessarily get to it until
> the next day.
>
> And finally, if a patch is reverted, it would be a good idea to send a
> personal e-mail.  It's sometimes hard to wade through all of llvm-commits
> looking for a revert that might or might not be there.
>
> It's a process issue.  We can always improve processes.
>
If you can't address a pulled revision, then just reapply that to a
source tree, work on the fix, then recommit it to the repository.
There shouldn't be a problem here. I do this all of the time to
everyone, including Chris, my manager Evan, me . . . everyone. I have
a zero-tolerance policy in place because it's crucial for us to keep
the tree healthy. (In reality, it's not *exactly* zero, if I have
access to the person and it's obvious that it's a minor problem, then
I'll ping them.)

-bw




More information about the llvm-commits mailing list